\n| ExplorerWorkspaceAdministrator<\/td>\n | Explorer workspace administrator<\/td>\n | Workspace view\/edit\/delete<\/td>\n | Full access to Workspaces (all public ones and your private one)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n- In P2.Security.Connect, Application Roles were mapped to actual Roles (global role mapping<\/strong>). The role that was mapped to the Application Role will receive the above privileges as well as <\/em>their migrated privileges.
\n \u00a0<\/li>\n- In order for any of these to be migrated, ensure that the names of the previous Server and Explorer \"applications<\/strong>\" (as defined in the old config tools under the Security tab) are specified in the Migration Utility.<\/li>\n<\/ul>\n
\nWrite Tag Privilege<\/h2>\n\n- Any datasources with the Write Tag<\/strong> check box selected (in Server Management) will receive the Write<\/strong> privilege for the Everyone role.
\n \u00a0<\/li>\n- The Write Tag<\/strong> check box for datasources will now be used as a method of turning off the Write Tag feature for a datasource (making it read only). If not selected, no user will be able to write to the datasource.
\n \u00a0<\/li>\n- In order for the Write<\/strong> privilege to work, the Write Tag<\/strong> check box for the datasource must be selected.
\n \u00a0<\/li>\n- When it is not selected, the UI still allows you save Write<\/strong> privileges, however this will not work unless the Write Tag<\/strong> check box is selected on the datasource.<\/li>\n<\/ul>\n
\nComments<\/h2>\nA comment will not be migrated if:<\/p>\n \n- The comment text is empty<\/strong>.
\n \u00a0<\/li>\n- There is no attached object<\/strong> (which is either a tag, entity, or entity attribute) or it is blank.
\n \u00a0<\/li>\n- It can\u2019t resolve the attached object. Note that the entity attribute is time-aware<\/strong>.
\n \u00a0<\/li>\n- It can\u2019t resolve the entity attribute at the Start Time<\/strong> of the comment. If the Start Time is null, it will try the End Time; if the End Time is null, it will try the comment Time (creation time).
\n \u00a0<\/li>\n- Other cases where the data might have to change:
\n \u00a0<\/p>\n\n- It can\u2019t find the user<\/strong> that made the comment. If this happens it will assign the default Admin user.
\n \u00a0<\/li>\n- The Last Modified<\/strong> time is less than the Creation time of the comment. If that happens, it will make the last modified time the same as the creation time.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
\nStyles and Style Constants<\/h2>\n\n- The GUID\u00a0<\/b><\/span>identifier has to be unique in the database. If it is not, it will take the first one with that GUID. The GUID is the identifier that Explorer uses to specify styles in their pages.
\n \u00a0<\/li>\n- Name<\/strong> has to be unique. If it is not, it will be given a different name such as \u201cOriginalStyleName (1)\u201d.
\n \u00a0<\/li>\n- Name has to be less than 200<\/strong> characters. If it is not, it will be truncated.
\n \u00a0<\/li>\n- The style property must have either a link to a Style Constant or a value<\/strong>. The value can\u2019t be blank. If both are specified, it will use the Style Constant.
\n \u00a0<\/li>\n- Styles and Style Constants will be migrated with the same GUID, which will be their GlobalId<\/strong> (to be used for import\/export when it is eventually added). This also ensures the pages get their styles.
\n \u00a0<\/li>\n- Styles will no longer be referenced by GUID. The migrator will replace all style GUID in pages with the style name<\/strong>. If the style cannot be found (it is missing or wasn\u2019t migrated), the reference to the GUID will stay in the HTML, but the style won\u2019t be applied. If the page is edited later and a different style is applied it will overwrite the value.<\/li>\n<\/ul>\n
\n |
![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2018\/05\/authentication-46a.png\")
<\/a><\/p>\n