Map Plant Issues to Gensuite Concern Reports

Configure a real-time outbound Issues integration and map its fields and picklist values for a plant.

Add one Issues integration for each plant that sends Issues to Gensuite. Field-name mapping (step 4) and value translation (step 5) are separate settings.

  1. In Integrations Manager, select the Gensuite card in the Connections panel.
  2. Click Add Integration.
  3. Set the header fields.
    FieldValue
    Select Integration PointIssues
    Data SynchronizationReal-time
    URL Path/concern/reports (appended to the Base URL)
    PlantThe plant whose Issues are sent
    Figure 1. Issues integration header fields (plant masked)

    Edit Integration dialog with Issues, Real-time, URL Path /concern/reports and the Plant field

  4. Under Data Mapping, select each mRounds field to send and enter its Gensuite field name in Destination Data Attribute.
    CBO(Source) Data Attribute (mRounds)Destination Data Attribute (Gensuite)Note
    TitleDescriptionRequired by Gensuite (greyed, preselected)
    Type of ROCTypeRequired by Gensuite (greyed, preselected)
    ROC - UnitDepartment
    ROC - Closure CommentCloseComment
    ROC - Closure DateCloseDate
    PlantSiteIDMust match the Gensuite Site ID
    Assign toAssignedtoRequired by Gensuite (greyed, preselected)
    Issue IDExtID
    Created BySubmittedBy

    The table lists the nine field mappings confirmed for this integration. Use the Concern Report field names of your Gensuite tenant; the names above are from one configuration. Greyed, preselected rows are required by Gensuite and cannot be cleared. Any other selected row needs a Gensuite destination; if it has none, clear the row.

    Figure 2. Partial view: confirmed mappings ROC - Closure Comment, ROC - Closure Date and Plant, with the ROC - Status values

    Data mapping rows: ROC - Closure Comment to CloseComment, ROC - Closure Date to CloseDate, Plant to SiteID, and ROC - Status values Open and Closed

  5. For each picklist field, open its value panel and enter the Gensuite value for each mRounds value.
    FieldmRounds value (example)Gensuite value (example)
    Type of ROC → TypePsip - 52 Weeks Of EhsPsip - 52 Weeks Of Ehs
    Type of ROC → TypePsip - Gelled ReactorPsip - Gelled Reactor
    Type of ROC → TypeEhs - RecognitionEhs - Recognition
    ROC - Unit → DepartmentLeading IndicatorsLeading Indicators
    ROC - Unit → DepartmentLxfLXF
    ROC - Unit → DepartmentTest Unit 1Test Unit 1
    ROC - StatusOpenOpen
    ROC - StatusClosedClosed

    Values are case-sensitive (for example, Lxf maps to LXF). The values above are examples from one plant. Map the standard Status values (Open, In-progress, Resolved) as agreed for the deployment.

    Figure 3. Example value mappings for Type of ROC and ROC - Unit

    Value panels mapping Type of ROC values and ROC - Unit values, including Lxf to LXF

  6. Click Save.

    The integration appears as Issue, Outbound, Real-time.

    Figure 4. Saved integration: Issue, Outbound, Real-time

    Integrations Manager with the Gensuite connection selected and one Issue, Outbound, Real-time integration

To change an integration, click the More icon (…) in the Actions column and select Edit.

The green check on the connection confirms the connection test only. Confirm that a test Issue creates a Concern Report in Gensuite before go-live.