You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Errors may occur during modeling or when running apps. To facilitate troubleshooting,  Scheer PAS Designer displays appropriate error and notification messages. With the Validation panel the Designer even provides a troubleshooting tool directly in the editor. On this page we have compiled an overview of the possible information and error messages in the Designer.

Sample data is displayed in gray.

Toast Messages

Toast MessagePossible ReasonSolutionFurther Information

An error occurred while deploying the service

  • No proxy port has been set in the service properties.
  • The used service port is already in use for another service in the integration component (Bridge).
  • If you are using forms within your BPMN model, insert 5444 as standard proxy port.
  • Open the integration component (Bridge) and check if the port already in use. If so, insert a free service port in the service properties.

Repository can not be exported due to compilation errors

  • No proxy port has been set in the service properties.
  • Service cannot be compiled correctly.
  • If you are using forms within your BPMN model, insert 5444 as standard proxy port.
  • You are able to download the repository or the Angular project only if the service has been compiled correctly. Check the validation panel for errors and solve them first.

Validation Panel Messages

If errors in the validation panel occur, try clearing the compiler cache. This could always helpful to resolve displayed compiler errors.

You can find the option in the additional menu of the Controls panel.

Validation Panel MessagePossible ReasonSolutionFurther Information

REST interface classes: urn.AddressImplementation.Address.Public.Address, urn.Data_Model.com.Address share common class name 'Address' but class names in REST interface must be unique.

There are duplicate class names in your model.

Your BPMN model name (in our example: Address) and a class of a BPMN message (in our example com.Address) have the same name. Rename the BPMN or message class.

Version of the project ('21.2') is not compliant with semver format (major.minor.patch).

The version number of your service is not written in the correct notation.

Change the version number of your service. The number must follow  Semantic Versioning 2.0.0:    Major.Minor.Patch . A pre-release tag is optional.

javax.ws.rs.ProcessingException: java.io.IOException: Error writing to server

The deployment took to long and ran in a timeout.

Check if all service properties are set correctly. Reload the Designer and restart the deployment of your service.

Errors during Application Execution

Erroneous BehaviorPossible ReasonSolutionFurther Information
Clicking on a button has no effect.It is not defined which process flow should be triggered when clicking this button.The trigger event is not set. The trigger event defines which button event should trigger the execution of the related element. You can find the attribute Trigger Event in the attributes panel of user tasks and boundary events.
The expected form is not displayed during execution.The form is not assigned to the corresponding process step.You need to assign the form to the corresponding user task.

On this Page:
Related Pages:

  • No labels