Registering New Security Types - Registering New Security Types - If you want to add new security types beyond the ones already created by Guidewire, you will need to follow these steps to ensure the security policy is aware of them. - Content Innovation Cloud - Hyland for Guidewire BillingCenter - Current/Hyland-for-Guidewire-BillingCenter/mke1773684524520 - Current - Current

If you want to add new security types beyond the ones already created by Guidewire, you will need to follow these steps to ensure the security policy is aware of them.

1. Open Guidewire BillingCenter’s source code.
2. Open the BillingCenter/modules/configuration/res/HFGWDocumentSecurityTypeMappings.properties file in a text editor such as Notepad.
3. Add a new line to the file and add a new key-value pair.
   The key is the document security code (exactly what is returned by document.getSecurityType() inside Guidewire BillingCenter). The value is the GUID of the new user group in the Hyland Content Innovation Cloud that contains a list of all users allowed to view documents of this type.
4. Redeploy BillingCenter.
5. Open the Studio Modeler application in the Hyland Content Innovation Cloud.
6. Click on the Guidewire BillingCenter Workspace project.
   The project window is displayed.
7. Click the Upload doc to Guidewire BC process in the Process Automation pane on the left.
   The project page is displayed.
8. Click Edit Process Variables in the Properties pane on the right.
   The Process variables page is displayed.
9. Click the Create Process Variable button and create a new Input/Output string variable. For example: docSecurityGuidCustom
10. Click the Calculate Document Security ID script in the Scripts section of the Process Automation pane on the left.
    The script is displayed.
11. Click Edit Script Variables in the Properties pane on the right.
    The Script variables page is displayed.
12. Click the Create Script Variable button and create a new script variable mirroring the existing in_docSecurityGuid variables.
13. Add a new var line at the top of the script for your custom security type, using the same format as the other security type var lines. For example: var SECURITYTYPE_Custom = "Custom";
14. Add a new case paragraph in the switch section that references your new var, using the same format as the other security type case paragraphs. For example:

    case SECURITYTYPE_Custom:
            variables.out_docSecurityID = variables.in_docSecurityGuidCustom;
            break;

15. Click Save (the cloud icon at the top bar of the pane) to save the script.
16. Navigate to the Upload doc to Guidewire BC process diagram and click on the Calculate Document Security ID task.
17. In the Properties pane on the right, find your new script variable in the input mapping section (for example, in_docSecurityGuid).
18. Click the edit button to set the script variable to the process variable configured earlier (for example, docSecurityGuidCustom).
19. Click Save (the cloud icon at the top bar of the pane) to save the process.
20. Select the Release action from the bar above the project window to release a new version of the project.
21. Open the Studio Admin application.
22. Navigate to Devops > Application Instances.
    The Application Instances page is displayed.
23. Find your Guidewire BillingCenter Workspace project and click Upgrade to upgrade it and update the script in your application instance.
    See the Hyland Automate Modeler documentation for general information on upgrading a project.