Controlling how Poetic applies multiple upgrade rules
Selecting the rule to use during upgrade activation
About the upgrade-from products
Mapping upgrade-from products to upgrade-to products
Handling non-whole number upgrade-to quantities
The Mapping tab lists the upgrade-from and to products for the automated upgrade job. The Mapping tab does not display for notification only jobs.
The upgrade-from and upgrade-to products are organized into upgrade rules. Each rule represents one upgrade option for this job. For example, if your upgrade-from products are available in multiple languages, you may set up one rule for each language. If the user has the English version of DocumentWriter V1, they get the English version of DocumentWriter V2. If they have the French version of DocumentWriter V1, they get the French version of DocumentWriter V2.
If the job has been executed, then users can only edit the information on the Mapping tab if:
If an upgrade job has more than one upgrade rule, then when you run the upgrade job, the Registry APPLY_ALL_MATCHED_UPGRADE_DELIVERABLE_RULES determines how Poetic applies the rules.
For example, an upgrade job has two rules:
The system includes entitlements for both Product A and Product X.
When the job runs:
During upgrade activation, if more than one upgrade rule could be applied, then Poetic uses the Registry setting UPGRADE_ACTIVATION_RULE_MATCH_ALGORITHM to determine which rule to use.
The possible values are:
FIRST_AVAILABLE | Poetic uses the first matching rule, and does not look at any of the other rules. This is the default value. |
MAX_MARKED | Poetic finds all of the mapping rules that could be used, and checks the number of marked entitlements on the machine for that rule. Poetic then uses the rule that has the most marked entitlements. |
The product type for upgrade-from products is based on the selection mode.
If product security categories are used (Registry IS_PRODUCT_SECURITY_CATEGORY_SUPPORTED is true), then you can only select upgrade-from products that belong to a product security category that you have the privileges to view.
Maintenance entitlements | Upgrade-from products must be maintenance products. |
License with linked maintenance | Upgrade-from products must be license products. If CAN_UPGRADE_MAINTENANCE_ENTITLEMENT is True, then there must be both license and maintenance products. |
License with related product line level maintenance at company level | Upgrade-from products must be license products. |
License without related product line level maintenance at company level | Upgrade-from products must be license products. |
License with related product line level maintenance at group level | Upgrade-from products must be license products. |
License without related product line level maintenance at group level | Upgrade-from products must be license products. |
License entitlements | Upgrade-from products must be license products. |
Products only | Upgrade-from products may be license or maintenance products. |
Loaded list of entitlements | If you are loading the upgrade-from entitlements from a flat file, then you do not need to provide upgrade-from products. When the job runs, Poetic automatically upgrades all of the entitlements in the file.
Note that if you do not provide upgrade-from products, you can only configure one rule, and the rule can only have one upgrade-to product. If you do provide upgrade-from products, Poetic checks the entitlements in the loaded file to see if they use those products and then only upgrades those entitlements that match. |
Upgrade-to products are the products received if a customer is eligible for the job based on the upgrade-from product(s) in the upgrade rule and the entitlement selection criteria.
In each rule, the first upgrade-to product is the product used to perform the upgrade. Additional upgrade-to products may be added. These additional products may be of any type. For example, when users upgrade from version 1 to version 2, they also get a free documentation set.
When selecting upgrade-to products:
Maintenance entitlements | Within each upgrade rule:
|
License with linked maintenance | Within each upgrade rule:
|
License with related product line level maintenance at company level | Within each upgrade rule:
|
License without related product line level maintenance at company level | Within each upgrade rule:
|
License with related product line level maintenance at group level | Within each upgrade rule:
|
License without related product line level maintenance at group level | Within each upgrade rule:
|
License entitlements | Within each upgrade rule:
|
Products only | Within each upgrade rule:
|
Loaded list of entitlements | Within each upgrade rule:
|
Within each rule, the upgrade-from products on the left make the user eligible for the upgrade-to products on the right. For example, you may use the upgrade rules to consolidate two separate products into a single unified product, or offer the upgrade plus a free documentation set.
Within each row, the product on the left makes the user eligible for the product on the right. So in this example, users with Acme DocumentWriter 1.0 receive Acme DocumentWriter 2.0, users with Acme PictureEditor 1.0 receive Acme PictureEditor 2.0, and users with Acme SpreadsheetWriter 1.0 receive Acme SpreadsheetWriter 2.0.
Line # | Upgrade-From | Upgrade-To |
---|---|---|
1 | Acme DocumentWriter 1.0 | Acme DocumentWriter 2.0 |
2 | Acme PictureEditor 1.0 | Acme PictureEditor 2.0 |
3 | Acme SpreadsheetWriter 1.0 | Acme SpreadsheetWriter 2.0 |
To replace one product with multiple products, leave the left column blank for the additional products. In this example, users with Acme DocumentWriter 1.0 receive Acme DocumentWriter 2.0, Acme PictureEditor 2.0, and a user's guide:
Line # | Upgrade-From | Upgrade-To |
---|---|---|
1 | Acme DocumentWriter 1.0 | Acme DocumentWriter 2.0 |
2 | Acme PictureEditor 2.0 | |
3 | Acme DocumentWriter User's Guide |
You can also replace multiple products with one product. In this example, users with Acme DocumentWriter 1.0, Acme SpreadsheetWriter 1.0, and Acme PictureEditor 1.0 receive AcmeOffice 2.0:
Line # | Upgrade-From | Upgrade-To |
---|---|---|
1 | Acme DocumentWriter 1.0 | Acme Office 2.0 |
2 | Acme SpreadsheetWriter 1.0 | |
3 | Acme PictureEditor 1.0 |
In this example, users with Acme DocumentWriter 1.0, Acme SpreadsheetWriter 1.0, and Acme PictureEditor 1.0 receive both AcmeOffice 2.0 and Acme ImageManager 2.0:
Line # | Upgrade-From | Upgrade-To |
---|---|---|
1 | Acme DocumentWriter 1.0 | Acme Office 2.0 |
2 | Acme ImageManager 2.0 | |
3 | Acme SpreadsheetWriter 1.0 | |
4 | Acme PictureEditor 1.0 |
When the upgrade-to quantity is calculated using a multiplier, the multiplier value may be a decimal value. For example, if the unit of measurement for a product is changing from MB to GB, then the quantity for the upgrade-to quantity might be calculated as .001 of the original quantity. Note that decimal values are only permitted if you are marking entitlements as upgradeable. You cannot use decimal values for upgrade jobs that generate upgrade orders or shipping files, or for jobs that replace entitlements.
On the Mapping tab, the For non-whole upgrade-to quantity dropdown determines what Poetic should do if the calculated upgrade-to quantity is not a whole number. The options are:
Error | When the calculated upgrade-to quantity is not a whole number, Poetic returns an error. |
Round up | When the calculated upgrade-to quantity is not a whole number, Poetic rounds up to the next whole number. |
For example, an upgrade job is configured to have the upgrade-to quantity be .25 of the upgrade-from quantity.
An eligible entitlement has a quantity of 25, so the upgrade-to quantity calculates to 6.25.
To add a rule, click Add upgrade rule.
To delete a rule, click the Remove rule link for the rule.
To add a line within a rule, click the Add blank line link for the rule.
To add multiple upgrade-from products to a rule, click Add from products. Use the Search Products form to search for and select the products. Each selected product is added as a new line within the rule.
To remove a line from a rule, click its Remove link.
For each upgrade-from product:
Required for Upgrade | If the product must exist on a system in order for the upgrade to occur, check the Required for Upgrade check box. |
Use for Marking | The Use for Marking check box determines which entitlements or machines or registration certificates to mark as upgradeable. To mark entitlements for the selected upgrade-from product, check the Use for Marking check box. |
Upgrade-From Product # | In the Upgrade-From Product # field, type the product number of a product that is being upgraded. To search for and select a product, click Find. |
For each of the upgrade-to products:
Upgrade-To Product # | In the Upgrade-To Product # field, type the product number of a product users are eligible for if they meet the upgrade-from requirements. |
Determine Qty From | From the Determine Qty From dropdown, select which entitlements to use to determine the quantity for the upgrade-to product.
To determine the quantity based on the quantity of the upgrade-from product, select Upgrade-from. To set the quantity based on the quantity of the validation entitlement, select Validation entitlement. Do not select this option if there is no entitlement validation. |
Qty Mode | From the Qty Mode dropdown, select the method to use to set the quantity.
|
Adjust by | In the Adjust by field, set any quantity to add to or subtract from the quantity determined using the Qty Mode and Qty fields.
For example, to subtract 3 from the quantity, type -3 in the Adjust by field. To add 5 to the quantity, type +2 in the Adjust by field. |
Unit price (%) | Enter a value to calculate the upgrade-to product net price based on a percentage of the upgrade-to product unit price. For example, if the unit price for Product A is $100, and you enter a unit price percentage value of 50, then the calculated upgrade-to product net price is $50.00. |