Design Request

Workflow Diagram (click to open)

• BPMN Icons
  • Start Event
  • Human Task
  • Update Data
  • Throwing Message Intermediate Event (HTTP)
  • Catching Message Intermediate Event (HTTP)
  • End Event

Download

designing_request-call-20180219-218-en.qar

Only available for Professional edition.

Notes

• Please change the following settings in edit mode after installation
  • In the Throwing Message Intermediate Event (HTTP), set the URL and API key of the target Message Start Event (HTTP) to connect to
    • URL: Replace YYY in “Access URL “$ {var [applicationRoot]}System/Event/MessageStart/YYY/2/start” on the Communication Settings tab with the number part of the App ID of the target App to connect
    • API key: Replace the Parameter Value of the item in Parameter Name “key” on the Send Parameter tab with the character string displayed in the API key of the Start Event of the target App to connect
• In the Update Data “1x. URL set”, replace the XXX in the expression “$ {var [applicationRoot]} System/Event/IntermediateMessage/XXX/4/receive” with the number part of the App ID of this App

Arrangement Tips

• The following Apps are published to be connected to
  • Designing Request Handlilng
  • Graphic Design Request Handling
• This App is focused only on the “request the design team” scene
  • Please use it as a design request process in various business flows by expanding this application, etc.
    • e.g.: Request a pamphlet design when the launch is decided in the Product development flow

See also

• Scenario: Episode 575: Business Improvement in SaaS Vendor Operation (Part 2)
• Settings Required When Importing an Archive
• Manual: M225: Auto Sending of HTTP Requests with Business Data Inserted
• Manual: M226: Standing by HTTP Request
• Manual: M411: Auto-starting a “Billing Process” Triggered by a “Shipping Process”
• Reference: R2272: Automatic Assignment to String-type