Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

* We are recommending the use of the Translation Workbench and overwrite/translate picklist values and record types. This will not be changed by the package upgrade. Additionally you can safely add your own values. Exception to this are global label values (see below).

1.2 After the Update 

  • Always check the latest Change Log to make sure your picklists and record types are up to date and work with the new features. Also make sure to not use deprecated objects or fields any more.
  • Check the Global Value Sets (Global Picklists) for Spring 2018 and up. Salesforce changed the behavior of global value sets in all managed package upgrades to match the behavior of standard value sets. Therefore you will now have to manually update any of ADvendio's global picklist with 
    • Label and API names for non-packaged individual values don’t change.
    • Global label values change back to the standard package values with each upgrade!
  • Enable new features (see below)
  • Reschedule Apex Jobs for ADvendio classes after an update to ensure the correct function.

...

3. General Recommendations

To upgrade safely please adhere to the following recommendations:

3.1 Dos

  • Keep as close as possible to the standard.
  • Think about changing internal processes first before changing the system.
  • Before developing custom functionalities on your own, ask you ADvendio consultant if there is already something similar on the roadmap or if ultimately an existing feature could be enhanced.
  • Read the release notes carefully.

    • In case of any questions, please don´t hesitate to contact us.

    • Pay special attention to all custom developments which might be interacting with ADvendio

  • Use a sandbox to test a new version before installing it in production
  • Determine your own release cycle and reserve resources (especially human resources) to implement own development and Advendio releases.
  • Use as many as possible of the embedded standard workflows and processes

  • Use the provided JavaScript API to embed your own business logic to the media configuration and commercial optimizer

  • Reschedule Apex Jobs for ADvendio classes after an update to ensure the correct function.

3.2 Don'ts

  • Don’t install a release without testing it in a sandbox!
  • Don’t integrate Custom JavaScript in the Media Configuration which works contrary to logic, workflows or processes in the standard of the ADvendio package.

  • Don’t re-develop a function on your own that is already part of the ADvendio Package.

  • Don’t use the same API names for objects or fields in ADvendio objects which are already defined in the package. An object or field in an ADvendio object even without prefix (in its API name) will be considered part of a component of ADvendio which leads to incorrect behavior in ADvendio.

  • Avoid to use validations for "irrelevant" data-changes in order to prevent errors in automated processes (e.g. when validating an account phone number, check if the number had been changed - don’t start this validation if other fields have been updated only.)

4. How to adapt or enable new ADvendio features

Some of the new features can't be packaged in Salesforce and therefore need manual work in order work correctly. Especially if you are upgrading and not installing a first version, some values have to be manually set.
The first step is to read newest Change Logs.  Change logs can be found next to the release notes in the corresponding seasonal release folder. The Change Log lists all values and fields which you need to consider if you like to introduce a new feature. 
So please consider the following if the new feature uses:
  1. Record types you might have to
    1. add them manually using the correct spelling from the change log and
    2. translate or overwrite the value into local language
    3. adjust the access rights for the corresponding user profiles. 
  2. Additional picklist values, make sure to
    1. add them manually using the correct spelling from the change log and
    2. translate or overwrite the value into local language
    3. add them to the correct record type(s)
    4. and adjust the access rights to the profiles which need.
  3. New fields or deprecated fields in Layouts
    1. Adjust your layouts appropriately to add new fields and their visibility. 


...