Custom Fields Usage

at the heart of software development, custom fields stand as essential key value pairs that empower developers to intricately define and deliver personalized information to end users through licensing this approach offers a range of applications, such as defining distinct license types like development, academic, government, or commercial, establishing designated account managers, facilitating seamless notification delivery, and even transmitting json data directly to the application this tutorial aims to help you grasp the use, implementation, and management of custom fields, enhancing your proficiency in software development prerequisites completed the getting started docid\ lsfy9tq3vfq4roow9shkd tutorial, including initialized licensemanager (or licensehandler ) with your configuration using the appropriate settings created a licenseid using either licenseid fromkey or licenseid fromuser function, depending on the activation method you prefer activated a license of any type implemented routine local and online checks within the application understanding custom field usage some examples of usage scenarios for custom fields include product identification and differentiation with custom fields, you can effortlessly categorize multiple products under the same custom field key but with distinct values, streamlining differentiation this minimizes code adjustments between product types, requiring only minor updates such as the product code and possibly a key and user information additionally, renaming a product becomes hassle free – by creating a custom field for the product name and updating it on the licensespring platform seamless notifications imagine creating a custom field object labeled 'notification' where the value serves as your notification message should you wish to modify your message, it's a breeze navigate to your product's custom fields, locate the 'notification' key, and update the value with the new message once users update their licenses through online checks, the new notification message is seamlessly integrated tailored edition configuration exploit custom field values to configure available editions for end users without requiring separate software distributions for instance, a licensetype custom field could embody values like "lite," "standard," or "pro " depending on the custom field value associated with a license, users can access different editions of the application, eliminating the need for multiple binaries defining custom fields to integrate a custom field for your chosen product, start by navigating to the desired product within the interface, locate and click on the designated "custom fields" tab here, you'll find the option to initiate the customization process by selecting "add custom field " on the pop up, take the opportunity to define the default key value pairing, effectively establishing the foundation for your custom field's configuration how to define a new custom field specify the default key value pair for the new custom field adjusting value of a custom field modifying the value of a custom field is a flexible option available to you at any point note to learn how to programmatically set a new value to your custom fields when issuing a license by looking at the documentation on our order docid\ dfmlvcglu4fhrne1qknfh begin by generating the new license for detailed instructions on how to issue a new license, refer to issuing new licenses docid\ feddg9wixsybhadhxyol0 once the new license has been created, locate it within the system and access the license screen here, you'll find the "custom fields" option; select it navigate to the custom field of the license, and click on the pencil tool in order to edit the value utilize the pencil tool to trigger a pop up window, enabling you to modify the value associated with the custom field for that specific license set new value for your custom field retrieving custom fields a custom field essentially consists of a pairing of a key and a value all the custom field data is stored within the local license accessing this data is achieved through std vector\<customfield> customfields = license >customfields();customfield\[] customfields = license customfields();list\<customfield> customfields = mylicense getdata() getcustomfields(); swift let customfields = license customfields // \[customfield] response = license custom fields() print(response)// go sdk v2 fmt println(license data customfields) upon license activation, whether through online or offline means, the resultant local license file encompasses all associated custom fields nevertheless, considering the dynamic nature of custom fields that can be introduced, removed, or modified post issuance and activation, an alternative method to refresh your local license file with any such alterations involves conducting an online check as shown one our license checks docid\ ie dah13b4dqxmaqoygrj tutorial