Good to know
This topic describes remarks/restrictions concerning labeling.
Module | Remarks | ||
|---|---|---|---|
Enterprise Talk | • External storage locations are excluded from labeling. Import analysis and logging will list this as an item requiring attention. A message will clarify that the user must transfer the system setting external data storage or configure it manually in the target environment and link it to the Enterprise Talk definition. • User-defined business objects must be available in the target system otherwise the import will be blocked. • Custom import/export workers must be available in the target system, or the import will be blocked. | ||
TSIs | When any of the following items is used/applied on a TSI, Labeling will take it over: • Selection step filters • User filters • Customizable lists • Selection step groups As a result, these items will be present in the export and import analysis reports. | ||
Layouts | Labeling will only take over the 'layout', the 'navigation actions' and their subsequent translations. | ||
SDI | The current export/import for SDI only takes over the template, not the filled data sheet. | ||
Standard orders | • Questionnaires and the related questions and answers are labeled. • Links (to asset groups, properties, space categories) are shown as dependencies. • If a linked user group is not present in the target. environment, this is flagged as a dependency conflict. • The standard order hierarchy (subs, lines, costs, ...) is labeled. • Reference fields to data are mentioned in the import analysis when missing in the target environment. The following issues are blocking: ◦ A mandatory field is missing in the target environment. ◦ A mandatory field is not in use in the target environment. ◦ When fields are not of the same type. • Standard order is labeled when linking a m-n standard order with a questionnaire. | ||
Questionnaires | • When a questionnaire is linked to a standard order, this too is labeled and exported. • The questionnaire 'hierarchy' is included (sub-questionnaires, questions, answers). • Questionnaire is labeled when linking a m-n standard order with a questionnaire. • For Standard gateways: ◦ Questionnaire and Question are labeled independently when a corresponding field is filled on a gateway: - When a Questionnaire field is filled, label Questionnaire. - When a Question field is filled, label Question. ◦ When an Answer option is filled on Standard sequence flow, label corresponding Question on gateway. • The QQ code system has been adapted to accommodate changing the QQ names to make it easier to transfer questionnaires, questions and their answer options between systems. When a question is linked to a questionnaire, the (M-to-N) table with the link gets filled with a generated QQ code. This QQ code is then used in PSS2 for identifying the questions from the questionnaire that can be linked to a PSS2 form. However, when exporting and importing PSS2 forms into a target system, the QQ codes must exactly match with the source system otherwise the questions will not be added to the PSS2 form, and related functionality (such as dynamic behavior) would be erased. | ||
User groups | • Users & User settings linked to the user group will be labeled. • Linked Solution licenses, Product definitions are labeled. • When linked, function profiles and standard orders are mentioned as a dependency | ||
Users | • The user's password will NOT be taken over in the export. New accounts will get the default password; the password of existing users will remain as is in the target environment.
• Users whose data is anonymized due to GDPR are not included in the label. • Data references (email, language, property set, linked persons) are mentioned in the impact analysis. • Linked user groups will be labeled and taken over as well as the Solution licenses, Product definitions. | ||
ProCenter action filters | • The filter is labeled and included only when linked to a ProCenter filter. • User groups linked to a ProCenter action filter are also labeled. | ||
Function profiles | • Any change to BO rights results in labeling the function profile. • The Fields, Actions, Status transitions, and Extended actions referred to in BO rights are regarded as data references; these are not labeled in Field Definer. | ||
Attributes | • Includes attribute sets and its details • Does not include assets and standard assets linked to attributes; these are considered data that can be transferred by using Enterprise Talk. | ||
(System) settings | This includes the following System Settings: • Alerts settings • Connect for Outlook • External data storage • File locations • General • Improved features • Outgoing email • Reporting • Security • Web application Other settings: • Performance logging • Authorization settings (Authorization on/off and ProCenter filter on/off) • Approved messages • PMFS system settings • CI/Graphical assets viewer • CAD Integrator Specifics • Data panels are not included • Cloud settings will be read-only • Some settings may cause a cache refresh (File locations) | ||
Web services | To pass validation, make sure that: • Linked (UD)BOs are present in the target system. • Linked fields are present and enabled in the target system.
| ||
Approval conditions & definitions | • The link between contract and approval definition will not be labeled. • Linked business objects/fields must be available in the target system. • Linked fields determine which fields can be filtered on. • New conditions can only be added if the approval condition is not active yet. | ||
PSS forms and site | Sites • Typically, PSS forms are site-specific. Sites will only be labeled when they are added or changed. • A site's underlying structure is not labeled, unless these definitions are themselves labeled. • Deleting a site is not tracked. • When a web definition is labeled, its site is not labeled. However, the information is added to the export summary (for import). References • Web definitions can reference other definitions. These are mentioned but not labeled unless these themselves have been changed/added. • Referenced elements must be present in the target environment. System images • System images linked to a web definition are labeled/included in the export. JavaScript and CSS • Custom JavaScript and CSS that is applied via a file reference on the server will be mentioned in the import/export analysis. Status and status link • When a status is linked to a web definition, it is not labeled, but its dependency is mentioned in the export/import. Fixed filters • If not part of the web definition XML, fixed filters will be taken over in the export/import. Upload block • When a UDBO communication log type is not available in the target, this is listed as a conflict. |
