Skip to main content
Skip table of contents

Roster Manager - Initial Deployment Steps

Once you have purchased the Roster Manager iPart, a few initial deployment steps are required. 

1. Create Panel Sources

When users submit a request via the iPart, an entry is saved into CSI_RosterManager_Action as summary information. Details regarding the request are saved into CSI_RosterManager_ActionItem. 

Create 2 panel sources under RiSE > Panel Designer > Add Panel Definition

  1. CSI_RosterManager_Action

    1. Panel Name = CSI_RosterManager_Action

    2. Parent Type = Contact

    3. Select Multi-Instance

    4. Select Create Source

    5. Source Name = CSI_RosterManager_Action

    6. Add the following Field Properties

Property Name

Property Type

Length

Data to be stored

ActionKey

Text

36

Unique identifier (GUID) - Primary Key

Code

Text

30

Workflow action code

Status

Text

1

Status of transaction

A - Active
B - Busy
C - Cancelled
D - Done
E - Error

Message

Text

4000

Response message

Exception

Text

4000

Exception error

DateAdded

Date and Time

UTC date and time record was added

LastUpdated

Date and Time

UTC date and time record was last updated

  1. CSI_RosterManager_ActionItem

    1. Panel Name = CSI_RosterManager_ActionItem

    2. Parent Type = Contact

    3. Select Multi-Instance

    4. Select Create Source

    5. Source Name = CSI_RosterManager_ActionItem

    6. Add the following Field Properties

Property Name

Property Type

Length

Data to be stored

ActionKey

Text

36

Unique identifier (GUID) tie back to Activity record

ItemKey

Text

36

Unique identifier (GUID) - Primary Key

SelectedId

Text

10

(Effected) iMIS ID of the person being selected (altered/changed)

Blob

Upload File

Workflow definition compressed and serialized

Status

Text

1

Status of transaction

A - Active
B - Busy
C - Cancelled
D - Done
E - Error

Message

Text

4000

Response message

Exception

Text

4000

Exception error

DateAdded

Date and Time

UTC date and time record was added

LastUpdated

Date and Time

UTC date and time record was last updated

An additional panel source to store client specific action detail is recommended but not required. The above panel sources are used for logging and tracking purposes only. For easier reporting of the action detail each time the Roster Manager iPart is used, it is recommended to create a Panel Source that will store the action details specific to the user record that was selected for the action. This panel source is also a good place to store the answers to the additional information questions that will be used within the iPart. See "Information" section below. 

Example Panel Source 

  1. CSI_RosterManager_ActionDetails

    1. Panel Name = CSI_RosterManager_ActionDetails

    2. Parent Type = Contact

    3. Select Multi-Instance

    4. Select Create Source

    5. Source Name = CSI_RosterManager_ActionDetails

    6. Field Properties

      1. 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. *Note - Remember that there is no need to add ID or Ordinal fields as those fields are automatically created when creating the panel source.

Property Name

Property Type

Length

Data to be stored

Action

Text

100

Action "code" or "label" to see the action that was selected

TransactionDate

Date

Current Date when action was taken

LoggedInUserID

Text

40

Logged in User that completed action

CompanyID

Text

40

Selected ID where the action was completed

Date1

Date

Answer to a date field using in additional info section

Date2

Date

Answer to a date field using in additional info section

Date3

Date

Answer to a date field using in additional info section

File1

File Upload

File added in additional info section

File2

File Upload

File added in additional info section

File3

File Upload

File added in additional info section

Text1

Text

500

Answer to a text field used in additional info section

Text2

Text

500

Answer to a text field used in additional info section

Text3

Text

500

Answer to a text field used in additional info section

2. Create General Lookup Validation Tables

When the iPart sends a request to Azure to complete a workflow process, the following information is used to validate your Roster Manager iPart license. 

Create 2 tables under Settings > General lookup tables

  1. Table Name = CSI_CLOUDID

    1. Add a single entry

      1. Code = Cloud ID provided by CSI at time of purchase (Ex: DEVIMIS)

      2. Description = iMIS URL (Ex: devems.csiinc.com)



        Note: If you have multiple domain names that need to refer to the same CSI Cloud ID instance you can add another general lookup entry in the CSI_CLOUDID table and use the Expansion field to store the CSI Cloud ID. In this case the Code value will be discarded, and the Expansion value will be substituted instead. For example:

        • Code = DEVIMIS203A

        • Description = devems-staging.csiinc.com

        • Expansion = DEVIMIS203

  2. Table Name = CSI_CLOUDAPP

    1. Entry 1

      1. Code = ROSTERMANAGER_FUNCTIONURL

      2. Description = https://rostermanager-fn.cloud.csiinc.com

    2. Entry 2

      1. Code = ROSTERMANAGER_FUNCTIONKEY

      2. Description = Q-_1wMx_HuViERHAaYvCE_fEJFg0yKxTuudiVHP6VCedAzFuRJ-KYg==


3. Create Content Type

Create new content type under RiSE > Maintenance > Content Types

  1. Select the Custom folder

  2. Select New > Content Type

  3. Select Client-based (preferred)

  4. Name of Content Type = CSI Roster Manager

  5. Description of Content Type = CSI Roster Manager - iPart

  6. 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

  7. 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 


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.