Initial Deployment Steps

iMIS Power Suite - Roster Manager

Once you have purchased the Roster Manager iPart, the following deployment steps are required:

1. Create the panel sources
2. Create the general lookup tables
3. Create the content type

1. Creating the panel sources

The following panel sources must be created:

Do the following to create the panel sources:

1. Go to RiSE > Panel Designer > Panel sources.
2. Select Add new panel source:
   • Source name - CSI_RosterManager_Action
   • Parent type - Contact
   • Multi-instance - Enabled
3. Click Save.
4. Select Add new property, and add the following properties:

5. Go back to RiSE > Panel Designer > Panel sources.
6. Select Add new panel source:
   • Source name - CSI_RosterManager_ActionItem
   • Parent type - Contact
   • Multi-instance - Enabled
7. Click Save.
8. Select Add new property, and add the following properties:

9. Go back to RiSE > Panel Designer > Panel sources.
10. Select Add new panel source:
    • Source name - CSI_RosterManager_ActionDetails
    • Parent type - Contact
    • Multi-instance - Enabled
11. Click Save.
12. Select Add new property, and add the following properties:

13. Add other field types based on the data from the additional info section that you want to store, i.e. decimal, integer, yes_no, etc.

2. Creating the general lookup tables

When you complete a workflow using the Roster Manager iPart, iMIS checks your license information to make sure it’s valid.

Do the following to create the tables:

1. Go to Settings > General lookup tables.
2. Select Add new table:

   • Table name - CSI_CLOUDID

   • Code - Cloud ID provided by ASI at time of purchase (e.g., DEVIMIS)

   • Description - The iMIS URL.

     🚧

     Warning

     Do not include https:// at the beginning of the URL.

     • If you plan on using Roster Manager across more than one of your organizations' sites, then it is recommended to use the root domain of the iMIS URL to cover all subdomains. For example:
       • iMIS URL: https://members.example.com
       • Code: EXAMPLEIMIS
       • Description: example.com
     • If you have multiple domain names referring to the same Cloud ID instance, you can add another general lookup entry in the CSI_CLOUDID table and use the Expansion field to store the Cloud ID. In this case the Code value will be discarded, and the Expansion value will be substituted instead. For example:
       • iMIS URL: https://online.asi.com
       • Code: ASIIMISA
       • Description: asi.com
       • Expansion: ASIIMIS
3. Click Save & Continue.
4. Click Close.

5. From the General tables drop-down, choose (None selected).

6. Select Add new table:

   1. Table name - CSI_CLOUDAPP
   2. Code - ROSTERMANAGER_FUNCTIONURL
   3. Description - https://rostermanager-fn.cloud.csiinc.com
   4. Click Save & Continue.
   5. Code - ROSTERMANAGER_FUNCTIONKEY
   6. Description - Q-_1wMx_HuViERHAaYvCE_fEJFg0yKxTuudiVHP6VCedAzFuRJ-KYg==
   7. Click Save & Continue.
   8. Click Close.

   

3. Creating the content type

Do the following to create a new content type:

1. Go to RiSE > Maintenance > Content types.

2. Select the Custom folder.

3. Select New > Content Type.

4. Select Client-based (preferred):

   1. Name of Content Type - CSI Roster Manager
   2. Description of Content Type - CSI Roster Manager - iPart
   3. URL to the html file that is used to display items of this type at runtime - https://cdn.cloud.csiinc.com/apps/roster-manager/display.html
   4. URL to the html file that is used to configure content items of this type - https://cdn.cloud.csiinc.com/apps/roster-manager/configure.html