×

Please give details of the problem

Docs

Find

FAQ

Table of Contents

General

What do I have to do in order to use DigitalSuite Studio instead of the Advanced IDE?

To support you with a smooth transition from the Advanced IDE to DigitalSuite Studio, we will provide the complete Advanced IDE functionality until November 30th, 2020. You can work with it as usual until this date, and even after this date, applications developed with the Advanced IDE will continue to run without any need for action and without limitations. After this date, we will disable the Advanced IDE on all platforms.

DigitalSuite Studio provides the complete functionality of the Advanced IDE. Most of the modules, for example, the administrative ones like User Management or Role Management, are backward compatible with the Advanced IDE.

The ProcessModeler, Process Console, and Composite API modules are not backward compatible. Processes and composite APIs created in the Advanced IDE require a transition to DigitalSuite Studio at the latest when the Advanced IDE has been disabled and changes become necessary. However, we strongly recommend that you start the transition as soon as possible so that all your processes and composite APIs are available in DigitalSuite Studio before the Advanced IDE is permanently disabled. Details of the transition are described here. For transition-related FAQs, please check the Transition of Processes and Composites APIs section below.

For further information, please contact the RunMyProcess support. They will be happy to help you with all your questions. Additionally, you can always get in contact with us using the feedback form, which you can open by clicking the Support button on the DigitalSuite Studio button bar.

What will happen to my applications and resources after the retirement of the Advanced IDE?

Your applications will continue to run unchanged even after the retirement of the Advanced IDE. In order to manage and modify the applications and resources, you will need to use the corresponding DigitalSuite Studio modules.

Most of the DigitalSuite Studio modules are backward compatible with the Advanced IDE, and no changes to applications or resources are necessary. Processes, composite APIs, and their instances, however, require a transition before you can open them with the ProcessModeler, CompositeAPI, or Process Console modules of DigitalSuite Studio.

We strongly recommend that you start the transition of processes and composite APIs as soon as possible and before the Advanced IDE is disabled. Details of the transition are described here. For transition-related FAQs, please check the Transition of Processes and Composites APIs section below.

Why have you transformed the user interface?

The newly built DigitalSuite Studio is based on state-of-the-art web technologies. Our adoption of HTML5, the latest evolution of HTML, for DigitalSuite Studio eliminates Flash Player from our toolset. HTML5 comes with new elements, attributes, and behaviors, and a larger set of technologies that, in combination, allow the building of more diverse and powerful applications. In addition to building the new modules using cutting-edge technology, we have taken the opportunity to improve the user experience by simplifying the way users design and develop their applications.

Where can I find help when I have problems using Flash with the Advanced IDE?

Major browser vendors have already moved to providing Flash as a “click-to-run” plugin. This means that users must explicitly enable Flash if they want to use it. Flash is required by the Advanced IDE so you must enable Flash in order to use the Advanced IDE. This is not under the control of RunMyProcess, and happens to all Flash-based applications. For help on continuing to use Flash, we recommend that you either check your browser's information page or follow our DigitalSuite Studio Transformation page.

Once a DigitalSuite Studio module is released, will the Advanced IDE module still be available for regular use?

Yes, we will provide the complete Advanced IDE functionality until November 30th, 2020. After this date, we will disable the Advanced IDE on all platforms.

What happens to the administration applications?

The administration applications, accessible through the account’s personalized RunMyProcess homepage, provide quick access to certain features without the need to open the Advanced IDE. Designed for quick access to all available features, DigitalSuite Studio eliminates the need for these administration applications. Therefore, the following administration applications will be disabled at some point of time which is still to be announced: “My Settings”, “User Management” and “Usage Report”.

Will there be RunMyProcess experts who can help us with the transition?

There are no plans for dedicated online training or support as we expect the transition to be very straightforward. Online documentation is available here. For on-site assistance, please contact the RunMyProcess support.

Which web browsers are supported by DigitalSuite Studio?

For details, refer to Web Browser Compatibility.

Which languages are supported by DigitalSuite Studio?

English is the language that is currently supported. For information on additional languages, please contact the RunMyProcess support.

Access Rights

Why can I not access DigitalSuite Studio?

This could occur for one of the following reasons:

  1. You are not authorized to access DigitalSuite Studio. A user with an Administrator profile can grant you access from the User Management module. When editing your user data, there are checkboxes on the Restrictions tab that disable access to DigitalSuite Studio and the Advanced IDE. Unchecking both options will grant access, provided that no additional restrictions apply.
  2. Access authorizations are set in the administration applications, and you do not have access at project level. A user with an Administrator profile can grant this access by assigning you a role with access rights of type User in the required projects. This enables the modules on the homepage and in DigitalSuite Studio.
  3. The basic account setting that controls access as set in the administration applications is enabled for your account, but the administation applications are not used. A user with an Administrator profile can disable this setting.

Why can I not access the User Management module?

This could occur for one of the following reasons:

  1. You are not a user with an Administrator profile. This is required to access the User Management module.
  2. You do not have access to any module of DigitalSuite Studio. A user with an Administrator profile can grant you access from the User Management module. When editing your user data, there is a checkbox on the Restrictions tab that disables access to DigitalSuite Studio. Unchecking this will grant access, provided that no additional restrictions apply.
  3. You are not authorized to view other user accounts. A user with an Administrator profile can edit your user data and lift this restriction by unchecking it on the Restrictions tab in the User Management module.
  4. Access authorizations are set in the administration applications, and you do not have access at project level. A user with an Administrator profile can grant this access in the RunMyProcess - User Management project. This will enable the module on the homepage and in DigitalSuite Studio.

Why can I not access the Usage Report module?

This could occur for one of the following reasons:

  1. You are not a user with an Administrator profile. This is required to access the Usage Report module.
  2. You do not have access to DigitalSuite Studio. A user with an Administrator profile can grant you access from the User Management module. When editing your user data, there is a checkbox on the Restrictions tab that disables access to DigitalSuite Studio. Unchecking this will grant access, provided that no additional restrictions apply.
  3. Access authorizations are set in the administration applications, and you do not have access at project level. A user with an Administrator profile can grant this access in the RunMyProcess - Usage Report project. This will enable the module on the homepage and in DigitalSuite Studio.

Why can I not access the My Settings module?

This could occur for one of the following reasons:

  1. You do not have access to DigitalSuite Studio. A user with an Administrator profile can grant you access from the User Management module. When editing your user data, there is a checkbox on the Restrictions tab that disables access to DigitalSuite Studio. Unchecking this will grant access, provided that no additional restrictions apply.
  2. All users usually have access to My Settings. If access authorizations are set in the administration applications, you may not be authorized at project level. A user with an Administrator profile can give you the necessary access right in the RunMyProcess - My Settings project. This enables the module on the homepage and in DigitalSuite Studio.

Why do I not have access to the development modules, such as WebModeler and ProcessModeler?

You do not have access to DigitalSuite Studio. A user with an Administrator profile can grant you access from the User Management module. When editing your user data, there are checkboxes on the Restrictions tab that disable access to DigitalSuite Studio and the Advanced IDE. Unchecking both options grants access, provided that no additional restrictions apply.

As an administrator, how do I ensure that my users have access to the DigitalSuite Studio modules?

Refer to Access to DigitalSuite Studio for the steps that must be taken.

Composite API

Can I open the design of a composite API in both the Advanced IDE and DigitalSuite Studio?

The Composite API module of DigitalSuite Studio provides all features to create and edit composite APIs. It is not backward compatible with the Advanced IDE.

Composite APIs created in the Advanced IDE can be opened and edited in the Advanced IDE until November 30th, 2020. To edit them in the Composite API module, a transition is required. Details of the transition are described here. For transition-related FAQs, please check the Transition of Processes and Composites APIs section below. For further information, please contact the RunMyProcess support.

At the end of a composite API transition, you will create a new revision of the composite API in the Composite API module as the basis for your future work. The new revision cannot be opened in the Advanced IDE. However, you can revert to a previous revision, if necessary.

Process Console

Can I monitor process requests for processes created in the Advanced IDE in DigitalSuite Studio?

For monitoring process requests created in the Advanced IDE, you need to perform a transition or continue to use the Advanced IDE.

If you open a process request created in the Advanced IDE in DigitalSuite Studio, the transition is instantly performed and the process request is opened in DigitalSuite Studio. You can then modify it in the new Process Console.

Process requests are not saved in any way after their transition to DigitalSuite Studio. You can still manage and monitor them in the Advanced IDE. If you access them again from DigitalSuite Studio, the transition is performed again.

Details of the transition are described here. For further information, please contact the RunMyProcess support.

Will existing process requests be unmanageable after the retirement of the Advanced IDE?

Even after the retirement of the Advanced IDE, existing process requests will continue to work. You will be able to manage them in DigitalSuite Studio. However, a transition will be required to open them in the new Process Console.

The transition is instantly performed when you try to open a process request created in the Advanced IDE in DigitalSuite Studio. Afterwards, you can modify the process request in the Process Console.

Process requests are not saved in any way after their transition to DigitalSuite Studio. If you access them again from DigitalSuite Studio, the transition is performed again.

Details of the transition are described here. For further information, please contact the RunMyProcess support.

ProcessModeler

Can I open the design of a process in both the Advanced IDE and DigitalSuite Studio?

The ProcessModeler of DigitalSuite Studio provides all features to create and edit processes. It is not backward compatible with the Advanced IDE.

Processes created in the Advanced IDE can be opened and edited in the Advanced IDE until November 30th, 2020. To edit them in the ProcessModeler, a transition is required. Details of the transition are described here. For transition-related FAQs, please check the Transition of Processes and Composites APIs section below. For further information, please contact the RunMyProcess support.

At the end of a process transition, you will create a new revision of the process in the ProcessModeler as the basis for your future work. The new revision cannot be opened in the Advanced IDE. However, you can revert to a previous revision, if necessary.

Is there a limit to the number of steps that can be used in process designs?

The ProcessModeler introduces a grid system which is unlimited. This means that you can add as many steps as you need.

To facilitate adding elements to a process design, it is possible to insert space, both vertically and horizontally.

Is there a limit to the number of roles that can be used in process designs?

There is no limit imposed by the ProcessModeler. All lanes that are available in the customer's account can be used in process designs.

Schedules

Can I monitor schedules for processes and composite APIs that were created in the Advanced IDE in the DigitalSuite Studio?

Yes, the Schedules module is backward compatible.

Transition of Processes and Composite APIs

How do I perform the transition from the Advanced IDE to DigitalSuite Studio for a process or composite API?

You are asked if you want to perform the transition for a process or composite API when you open it in DigitalSuite Studio or the Advanced IDE. It is only necessary to perform the transition, if you want to view or edit the design of the process or composite API in the new ProcessModeler or Composite API module. The process or composite API will work as usual without going through the transition.

The transition may take some time to complete. Afterwards, you should check the design of the process or composite API carefully in the ProcessModeler or Composite API module. If you are satisfied with the result, you should save the process or composite API to create a new revision as the basis for your future work in DigitalSuite Studio. The new revision cannot be opened in the Advanced IDE. If the result does not meet your expectations, do not save the process or composite API. If you have already saved it, you can still revert to a previous revision.

Be aware that the new revision will immediately replace the previous one in any project version where it is included with the Keep updated option enabled. If the project version is running in Live mode, the new revision will be instantly available to all users in the production environment.

Details of the transition for processes and composite APIs are described here.

How do I proceed with the transition of processes which have subprocesses or include composite APIs?

If a process has subprocesses or includes composite APIs, we recommend that you perform the transition for the subprocesses and composite APIs first. After you have checked the results and saved a new revision of each subprocess and composite API, you can perform the transition of the parent process. Following this procedure makes it easier to identify and solve issues in the individual processes and composite APIs as when performing the transition of all components at the same time.

Keep in mind that the transition is only necessary to edit processes and composite APIs in the DigitalSuite Studio modules. A process will still work, if you perform the transition for it, but not for the subprocesses and composite APIs it includes, and vice versa.

What do I do if I'm not happy with the result of the transition?

In this situation, do not save the process or composite API for which the transition was performed. If you have already saved it, you can revert to a previous revision.

Do I have to perform the transition to DigitalSuite Studio for existing processes and composite APIs?

You can continue to use the Advanced IDE up until its end-of-life, scheduled for November 30th, 2020. Following this, processes and composite APIs will continue to work as usual but it will be necessary to perform the transition to DigitalSuite Studio to view or edit them.

However, we strongly recommend that you start the transition as soon as possible so that all your processes and composite APIs are available in DigitalSuite Studio before the Advanced IDE is permanently disabled. Details of the transition are described here.

Will I be able to modify existing processes and composite APIs after the retirement of the Advanced IDE?

After the retirement of the Advanced IDE, you will be able to manage and edit existing processes and composite APIs in DigitalSuite Studio. However, you will need to perform the transition to open them in the new ProcessModeler or Composite API module.

You are asked if you want to perform the transition for a process or composite API created in the Advanced IDE when you try to open it in the ProcessModeler or Composite API module. The transition may take some time to complete. Afterwards, you should check the design of the process or composite API carefully in the ProcessModeler or Composite API module. If you are satisfied with the result, you should save the process or composite API to create a new revision as the basis for your future work in DigitalSuite Studio. If the result does not meet your expectations, do not save the process or composite API. If you have already saved it, you can still revert to a previous revision.

Be aware that the new revision will immediately replace the previous one in any project version where it is included with the Keep updated option enabled. If the project version is running in Live mode, the new revision will be instantly available to all users in the production environment.

Details of the transition are described here.

WebModeler

Can I open a web interface in the Advanced IDE and DigitalSuite Studio?

Yes, the WebModeler is backward compatible.

Do existing web interfaces need to be migrated to the WebModeler?

No migration is required as the WebModeler is backward compatible.

What is the main difference between the new DigitalSuite Studio WebModeler and creating web interfaces in the Advanced IDE?

The WebModeler speeds up and simplifies the development of digital transformation projects. It delivers new, improved user experience with streamlined features, helping you to reduce the time to complete a solution on the RunMyProcess DigitalSuite platform, resulting in a faster delivery of solutions. New capabilities include easy-to-use drag-and-drop features and the ability to preview web interfaces prior to deployment, enabling easier test and verification of web interfaces before release.