![]() ![]() Messages can be complete, lost or found synchronous or asynchronous call or signal. Boundary, control and entity elements from robustness diagrams can also own lifelines. ![]() This will usually be the case if the sequence diagram is owned by a use case. Sometimes a sequence diagram will have a lifeline with an actor element symbol at its head. If its name is "self", that indicates that the lifeline represents the classifier which owns the sequence diagram. A lifeline will usually have a rectangle containing its object name. Sequence diagrams are not intended for showing complex procedural logic.Ī lifeline represents an individual participant in a sequence diagram. Sequence diagrams are good at showing which objects communicate with which other objects and what messages trigger those communications. But the activiti and camunda both had extend these element in a similar way.Ĭurrently, the WF Designer can only generate bpmn files that are executed on the activiti engine because the VFC uses the activiti engine.UML 2 Tutorial - Sequence Diagram Sequence DiagramsĪ sequence diagram is a form of interaction diagram which shows objects as lifelines running down the page, with their interactions over time represented as messages drawn as arrows from the source lifeline to the target lifeline. The reason is that the bpmn specification does not define elements other than flow control, such as form field, formProperty etc. There are some activiti extend elements start with prefix 'activiti:'. The input parameter definitions of the task. Map value is the header paramter name, such as ''application/json. Map key is the header paramter name, such as ' Accept'. The header paramters of the rest api associated to the rest task. Valid value as follow: get, post, put, delete The method of the rest api to be called while the activity be executed on the workflow engine. The path of the REST API relative to the API router exposed path. In the condition of access the REST API via MircoServiceBus, The workflow engine can query the URL of the REST API exposed through the MircoServiceBus by name and version. The microservcie version of the REST API. Only for the condition of access the REST API via MircoServiceBus. The Base URL of the REST API exposed through the API router.Ĭhoose between the 'url' field and ('name', 'version') filed. The body of the save request must be in a json format that specifies the metadata. If the Authorization header is missing, then an HTTP “401 Unauthorized” with ‘If “Authorization” header is received, but the client‘s authentication fails ( due to either unknown “username” or invalid “password” ) the “403 Forbidden” response code will be returned ![]() This string is then Base64 encoded to produce the encoded credential which is communicated in the header after the string “Authorization: Basic “. The username and password are formed into one string as “username: password”. Valid values are: “application/octet-stream” If this header with non-null value is not supplied the HTTP Request will be rejected with '400 Bad Syntax’ response code.ĭetermines the format of the body of the response. If it is not sent it will be automatically generated by SDC on request receipt.įor auditing purpose each component calling the SDC API should identify itself by sending its identity ( e.g. This user must also have a Designer role in SDCĪccording to the general ECOMP agreement the "X-ECOMP-RequestID" header with the transaction UUID should be published by ECOMP component calling an exposed by other ECOMP component API in order to make possible the transaction traceability across ECOMP. The value for this header must be the MD5 checksum over the whole json body Open the an existed workflow and navigate to the '(ZTE) WF Designer'.įor a new workflow, before it be opened, the catalog should create it first. Get Category Information of Extend BPMN Activities (from Catalog)ĭefine the Rest APIs of (ZTE) WF Designer, these APIs will be provided by ZTE.Get Extend BPMN Activites (from Catalog).Save Workflow Content with WF ID (to Catalog).The rest APIs of Catalog should be provided as follow: Open and Navigates to (ZTE) WF Designer.So, the rest APIs of '(ZTE) WF Designer' should be provided as follow: The interaction between Catalog and '(ZTE) WF Designer' is as follows: In this case, the Catalog plays a manager role of the workflows, it manage the designed workflows and provide the Create/Updata/Query operations of workflows for Service Designer and provide the storage of workflows.Īt the same time, the '(ZTE) WF Designer' plays an editor role of a workflow selected. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |