Journey Workspaces FAQ - Configuration

   WorkspacesThis topic is related to Journey Workspaces. |   Platform Developer |   18.11 This feature was introduced in 18.11. |   22.04 This feature was updated in 22.04.

Can the Applicant card or Background Check card be removed from the Workspaces UI?

Yes, the Applicant card and Background checks card can be removed from the Workspaces UI.

  • To remove the Applicant card: Add an empty applicants property inside the space JSON:

    {
        ...
        "applicants": [ ],
        ...
    }
  • To remove the Background checks card: Add an empty integrations property inside the space JSON:

    {
        ...
        "integrations": [ ],
        ...
    }

From Workspaces 19.11, these cards are integrated into custom cards. More information is available to help you understand how to configure custom cards.

Can the Timeline card or Documents card be removed from the Workspaces UI?

No, it’s not possible to remove the Timeline card or Documents card from the Workspaces UI.

How do I configure the views and table columns in the Workspaces List screen?

Click one of the links below for more information about how to configure views and table columns in the WorkspacesList screen.

How do I configure the Key info card in the Workspaces Details screen?

This feature was introduced in Workspaces 19.05. Click one of the links below for more information about how to configure the Key Info card in the WorkspacesDetails screen.

How do I configure the actions to be displayed for each Workspaces space?

This feature was introduced in Workspaces 19.05. Click one of the links below for more information about how to configure the actions available for each space.

How do I hide a step from the application timeline?

This feature was introduced in Workspace 19.05.

To hide a step, configure the Global JSON property to include the hideSteps attribute with the list of steps to be hidden. For example:

"hideSteps": ["Helpdesk View"]

For more information, refer to the Global configuration in the Workspaces technical documentation.

How do I restrict a Workspaces user to view only certain spaces in the Workspaces application?

Controlling user access to spaces using Journey Manager roles or groups was introduced in Workspaces 19.05.

To restrict a Workspaces user’s access to certain spaces, configure the spaces attribute in the Global JSON property with a list of roles and/or groups that are configured with the appropriate permissions.

  • Workspaces 20.05 – access to spaces is controlled in TypeScript configuration. For details, see Migration from v19.11 to v20.05 > spaces in the Workspaces technical guide

  • Workspaces 19.11 – configure the permissions attribute

    "spaces": [
        {
            "label": "Process",
            "icon": "BallotOutlined",
            "value": "Process",
            "permissions": {
                "type": "role",
                "value": ["Processing Staff", "Work Spaces Staff"]
            }
        },
        {
            "label": "Helpdesk",
            "icon": "HeadsetOutlined",
            "value": "Helpdesk",
            "permissions": {
                "type": "role",
                "value": ["Helpdesk Staff", "Work Spaces Staff"]
            }
        }
    ]

    More information is available to help you understand how to configure permissions in the Global configuration.

  • Workspaces 19.05 – configure the roles and groups attributes

    "spaces": [
        {
            "label": "Process",
            "icon": "BallotOutlined",
            "value": "Process",
            "roles": ["Processing Staff", "Work Spaces Staff"],
            "groups": ["Manual Review", "Fraud Review", "Error Review"]
        },
        {
            "label": "Helpdesk",
            "icon": "HeadsetOutlined",
            "value": "Helpdesk",
                "roles": ["Helpdesk Staff", "Work Spaces Staff"]
        },
    ]

    More information is available to help you understand how to configure permissions in the Global configuration.

Are job properties supported in the space JSON configuration for Workspaces?

No, job properties are currently not supported in the space JSON configuration for Workspaces.