This screen allows you to modify the configuration of your account. You can navigate to this page by choosing
Configuration from the
Account menu. Each category of configurable options is represented by a tab.
Account configuration Tab
The name of your company, this will be displayed next to the RunMyProcess icon.
The country where your company is based. Please note that this has no effect on RunMyProcess behaviour including the IDE's language - each user can choose their preferred language from the MySettings application.
Default domain name
The Domain name set up as the default one in the Domains Tab (where default check box is checked). This domain will be used for things such as Google OpenID authentication.
The ID of your account (
You can change the logo displayed in the upper left part of the IDE. This logo will also be displayed in the default header of your Web Interfaces. To choose a logo, click on the
Uploaded images button, a list of your uploaded files that are of type images will be displayed, once an image is selected, a preview is shown below the button:
Session timeout (sec)
You can modify how much time a session will remain open when there is no activity. By default this value is set to 3600 seconds.
All your domains are displayed here. To edit a domain, click on its name, then click on the edit button :
Your domain name (e.g. runmyprocess.com).
Check this box to specifiy that this is the default domain for your account. If you only have one domain, it will automatically be the default one. To change the default domain, edit the domain to be specified as default, check the default box and save, the previous default domain will no longer be the default domain.
Allow Secure Enterprise Connector connections
Check this box if you want to use this domain with our Secured Enterprise Connector. You can learn more on provider authentication and also learn how to install the Secured Enterprise Connector.
Secure Enterprise Connector login
Please enter your Secured Enterprise Connector login id here, as configured in your "localConfig.xml" file of your Secure Enterprise Connector agent. You can learn more on provider authentication and also learn how to install the Secured Enterprise Connector.
Secure Enterprise Connector password
Please enter your Secured Enterprise Connector password here, as configured in your "localConfig.xml" file of your Secure Enterprise Connector agent. You can learn more on provider authentication and also learn how to install the Secured Enterprise Connector.
User Metadata Tab
Click the [Add item] button, to create a new user attribute (e.g. department, address...).
The name of your new user attribute.
The data type of your new user attribute; it can be "text", a "number", a "date", a "boolean" (check box), an "array" (with different 'simple' value columns), a "structure" (e.g. an address has a street number, a street name, a zip code and a city) or a custom list. The attibute can be mandatory or optional.
Only a user with an ADMIN profile can modify a user's metadata .
Once saved, metadata name and type can't be modified.
User Preferences Tab
Click the [Add item] button, to create a new user attribute (like login, password on another application...)
The name of your new user attribute.
The data type of your new user attribute; it can be "text", a "number", a "date", a "boolean" (check box), an "array" (with different 'simple' value columns), a "structure" (e.g. an address has a street number, a street name, a zip code and a city) or a custom list. The attibute can be mandatory or optional and you can choose whether it should be secured or not.
Preferences can only be modified by the user it relates to.
Once saved, a preference name or type can't be modified.
These preferences can be used within RunMyProcess connectors or processes by using the
You can establish the rules for your password policy here. You can choose to limit the amount of possible login attempts and specify the maximum number of attempts allowed. Users who fail to login within the maximum number of attempts will be locked out of their accounts and the status of their account will be shown as black. Their account administrator will need to unlock their account before they can log on again.
3 authentication methods are available to connect to our platform :
- Login/password : connect to our platform using your RunMyProcess login/password. You can define your own custom login page that can be either a public web interface or a public html file downloaded on our platform;
- SSO with SAML V2 : connect to our platform using your samlv2 compliant identity provider;
- Google OAuth2 : connect to our platform using your Google account.
Please note that the Login/password method is always available, even if another method is selected in the authentication tab. Please note also that you can always start a Google OAuth2 authentication flow by adding
from=google&domain= in the url of the resource you want to access.
SSO authentication method
The URL of your samlv2 compliant identify provider redirect page. The user wil be directed to this page when requesting a protected resource in RunMyProcess, without an active session. If not connected to your federated environment, the user will be redirected to your SSO login page.
The URL you want to be used by RunMyProcess when a logout is requested by the user. This may be used to logout from all the applications available on your federated environment.
Account management redirect
Optional - the URL of your SSO management page.
Name Id Format
Name Id of the identity provider to be used to find the user name returned to RunMyProcess. When a user is connected in your SSO, RunMyProcess will recognise this user by the login id. This login has to be the email address of the RunMyProcess account. Please therefore ensure that the provided
Name Id is mapped to the field containing the email user on RunMyProcess user account.
Copy and paste here the identity provider certificate issued by your SSO application. The certificate must use the PEM format.
One Authentication method per execution mode
You can use a different authentication method for each execution mode (
ACCEPTANCE), so that, for example, you do not have to have real users in your production identity provider to test your applications.
You can use the same authentication method for all the execution modes, to do that easily, please use the copy/paste icons (1).
By default all accesses with no execution mode specified will be handled as LIVE executions.
You select the
Login/password method in the TEST tab.
You select the
Google OAuth2 method in the ACCEPTANCE tab.
You select the
SSO method in the LIVE tab.
|Access||Execution Mode||Method used|
|https://live.runmyprocess.com/live/customerId/appli/appliId||LIVE||SSO method is used|
|https://live.runmyprocess.com/live/customerId/appli/appliId?P_mode=TEST||TEST||Login/password method is used|
|https://live.runmyprocess.com/live/customerId/appli/appliId?P_mode=ACCEPTANCE||ACCEPTANCE||Google OAuth2 method is used|
If you have configured a Google OpenID authentication policy for the
LIVE execution mode, you will be able to configure the automatic provisioning of the users on your account.
To do so just check the
Auto-provisioning check box.
With this option enabled, a user, who does not have a matching RunMyProcess account, logs in to the platform, his or her account will automatically be created and configured.
The account created will configured as such :
- name : retrieved from Google
- login / email : retrieved from Google
- profile :
- IDE language : English
- Application language : English
The user created will be granted access to all the applications accessible to all the users of the account via an
If the account subscription model is User-based and id the number of users credit is insufficient, the user will be created with an
ACTIVE status and an
OVERDUE billing status.
Custom Homepage Tab
From here, you can configure your RunMyProcess account to perform a redirection from the RunMyProcess portal page to a personalized homepage. This can be achieved for each environment, namely:
|Desktop||Web access from a desktop environment|
|Mobile||Mobile access outside of RunMyApp|
|Tablet||Tablet access outside of RunMyApp|
|RunMyApp for Mobile||Mobile access using RunMyApp|
|RunMyApp for Tablet||Tablet access using RunMyApp|
More information can be found here.