Customer Accounts

Each customer registered with DigitalSuite corresponds to a tenant and has a unique account. Administrators of the customer can manage the account and configure it according to their requirements.

An account and its configuration comprises the following settings and considerations, which are described in detail in the sections below:

Table of Contents

Customer Accounts

Account Identification

The following settings identify a customer account and the company or organization represented by it:

Account Name: The name of the customer account, typically the name of the company. The account name is shown, for example, in the header area of DigitalSuite Studio.
Account ID: A generated number used to uniquely identify the account. The account ID is required, for example, to launch a process using JavaScript from a web page or to call any kind of DigitalSuite API. The account ID is available as a global variable, P_customer.
Country: The country where the company is located. The country does not determine the language used for the DigitalSuite user interfaces. The users can set their preferred language individually in their personal user settings.
Logo: An image related to the company. It is displayed, for example, in the header areas of web interfaces developed with DigitalSuite. The image file needs to be uploaded to DigitalSuite, for example, in the context of a project.

User Authentication

Users intending to work with DigitalSuite and the applications running on it need to be authenticated. The only exception to this is the access to public resources, which is possible for everybody without verification.

DigitalSuite supports different methods of authenticating the users of an account when they access the platform or an application:

Login/Password: Users log in with their email address and password stored in DigitalSuite.
Google OAuth2: Users connect to DigitalSuite using their Google account.
SSO with SAML 2.0: Users connect to DigitalSuite using the credentials of a SAML 2.0 compliant identity provider, single sign-on being supported.

For details on the individual authentication methods, refer to User Authentication.

Each execution mode of DigitalSuite can use a different authentication method. This means, for example, that there is no need to have real users in Google or the SAML identity provider system to test applications, as long as the Login/Password method is used for the Test mode.

A password policy allows customers to limit the number of login attempts. Users who fail to log in within the maximum number of attempts are locked out of their accounts. An administrator needs to unlock the accounts before the users can log in again.

Note about public resources: DigitalSuite allows customers to make resources of applications public for access by any person without authentication. For this to be possible, the customer account has to configured accordingly, which is usually done at the time it is created. If you encounter problems in manipulating public resources, please contact the RunMyProcess support.

Domains

Domains are administrative constructs required for specific purposes such as secure access to on-premise resources with DigitalSuite EnterpriseConnect .

Customers can create as many domains for their account as needed, using valid domain names such as my.enterprise.connect.com. Domains for DigitalSuite EnterpriseConnect also require a user name and password for authentication, which later is specified together with the domain name in the configuration of the on-premise EnterpriseConnect Agents.

Custom Homepages

By default, the portal page of DigitalSuite, https://portal.runmyprocess.com, redirects users to the development environment for creating and testing applications. This environment may be of little use to end users. For this reason, it may be desirable to restrict its access to designers, and configure a redirection from the portal page to a personalized environment and custom homepage for all users. This homepage could, for example, display a list of all the applications the current user has access to.

A separate custom homepage can be set for each of the following access environments:

Desktop: web browser access
Mobile: access through RunMyApp and web browsers
Tablet: access through RunMyApp and web browsers

The custom homepage may be an external web page or a web interface developed in DigitalSuite. In the latter case, a dedicated project accessible to all users should be used.

Homepage and Authentication

The homepage and authentication method configured for an account can be combined by using the https://portal.runmyprocess.com/{account_id} redirection.

This is useful if users log in to DigitalSuite with SAML 2.0 or Google OAuth2 authentication or from a custom login page and then should be redirected to a custom homepage.

Accessing https://portal.runmyprocess.com/{account_id} loads the account's authentication policy and performs the appropriate authentication steps and potential redirections. After a successful login, the user is redirected to the account's homepage.

Homepage Portal Application

DigitalSuite comes with a standard portal application, RunMyProcess - Homepage, which customers can use as the basis and example for developing their homepage.

The application consists of one web interface with a JavaScript widget and a stylesheet. It retrieves the accessible web interfaces of the customer account, including their description and thumbnail, and displays them on a page in sections ordered by the web interfaces' tags. The list is fully based on the permissions of the connected user for the individual web interfaces.

Customers can use the RunMyProcess - Homepage application as their own homepage, and adapt the web interface and stylesheet as required. For example, they can upload a logo to be inserted in the header of all their web interfaces.

User Preferences and Metadata

User preferences and metadata are means to add custom information as attributes to each user belonging to a customer account, for example, postal addresses, phone numbers, identifiers, accounts, passwords, or data required for applications.

User preferences: Each user can enter values for these attributes.
User metadata: Only users with an Administrator profile can enter values for these attributes.

Like other user settings, the preferences and metadata can be evaluated in applications. Different values can be specified for each execution mode of DigitalSuite.

The definition of user preferences and metadata consists of the following:

Name: Mandatory identifier of the attribute. The name cannot be changed later.
Data Type: Text, Boolean, Number, Date, Structure, Array or List. The data type cannot be changed later.
The specification whether a value for the attribute is mandatory and needs to be unique for a given execution mode.
For user preferences only: the specification if the value is secured and only visible to the user in question or also to other users.

Behavior of DigitalSuite

Customers can determine specific aspects of the behavior of DigitalSuite and its user interfaces by means of the corresponding settings at their account:

Session timeout: Determines how long a user session with DigitalSuite remains open during periods of inactivity. By default, this value is set to 3600 seconds.
Access to DigitalSuite Studio modules: Determines whether access to specific modules of DigitalSuite Studio is based on a user's profile and access restrictions set at user level only, or additionally depends on access rights defined for standard portal applications. For details, read Access to DigitalSuite Studio.

Standard Portal Applications

When a customer account is created in DigitalSuite, a number of applications are automatically copied to it. These applications are referred to as standard portal applications. They include DigitalSuite interfaces, documentation, utilities, templates, and examples. For more details, refer to Standard Portal Applications.