Software AG Designer
Business process developers receive a new business process model from a business analyst and use the Software AG Designer to implement business process models. Software AG Designer offers two perspectives for implementing business process models for two different types of business processes:
The new Dynamic Process Development perspective. Dynamic business process models are all-inclusive and can be executed without any compilation. You can deploy new versions quickly, and easily modify individual instances of processes in-flight.
The classic Process Development perspective. Classic business process models must be compiled into run-able elements before you can actually execute processes. Specifically, you must build and upload the model to create the XML scripts, triggers, flows, and metadata that will initiate and control a process instance at runtime. Each time you need to modify these models, you must edit and recompile.
Both Software AG Designer perspectives offer an extensive set of programming tools that enable a technical user to focus on the detailed implementation of a business process model.
Developers implement a business process model in Software AG Designer by dragging and dropping graphical representations of process steps onto a design canvas, then configuring each step to perform a specific function. For example, process steps can:
Receive data. Data can be in the form of documents from
Software AG products, JMS messages, and output data from web services and services such as database query services.
Subscribe to business documents on or publish business documents to
Universal Messaging.
Subscribe to business events on or publish business events to the event-driven architecture (see
Analytics & Decisions).
Invoke services such as flow services, web services, or rule services, or adapter services that in turn invoke programs on mainframes and UNIX systems.
Invoke rules, tasks, other business processes, or
Trading Networks.
Publish data for other business processes and services to consume.
Assign activities, called
tasks, to a user or group of users to perform. Tasks in turn can invoke rules, rule sets, and services.
Queue case instances in
AgileApps.
Business process developers define the way data passes through and is handled by your business processes. They define the order of steps in the processes, and the conditions under which the steps start, run, pass data, and end. Business Process Modeling Notation (BPMN) provides a graphical representation of the underlying model and of the functionality and behavior of its steps.
Business process developers can also define milestones within a business process model by defining stages. A stage spans process steps, has a start milestone step, and has a complete milestone step that must be reached within a specified period of time. For example, a stage might be defined as starting at the Receive Purchase Order step (start milestone), completing at the Ship Product step (complete milestone), and transpiring within three days.