Decision-Making Flow, Parallel Approval
The approval flow is designed to speed up the approval process.
Tasks are sent to several approvers in parallel. In addition, examples are pre-populated to make it easier to apply.
The approval flow is designed to speed up the approval process.
Tasks are sent to several approvers in parallel. In addition, examples are pre-populated to make it easier to apply.
The approval process switches the decision-maker depending on the amount of the application.
Applications of less than $5,000 are approved by the section manager; applications of more than $5,000 are approved by the department manager.
The decision result is notified to the applicant by email.
This item deletes files on Box. You can delete multiple files at once. When you delete multiple files, you should write one file ID per line.
This is a process that centrally manages everything from receiving inquiries to sending responses. After receiving the web form, AI will check the received content. If the call is determined to be a sales call rather than an inquiry, the caller will be assigned a different task from normal response.
Some modeling elements in Questetra can send HTTP requests, and in this way you can use them to call and utilize the REST APIs which are provided by many services.
This article explains the scope of authentication sharing and the various options that are available when creating HTTP authorization settings.
Three approvers are requested to authorise the draft in parallel.
When two or more approvals are received, the draft is considered approved.
The applicant is notified of the result by email.
Basic use of automatic processing ”DocRaptor: Generate PDF”.
This item posts a message to Slack. Blocks are available.
Gets the number of characters in the text. Consecutive blanks (including tabs and double-byte spaces) are counted as one character. The number of characters that do not count linefeed codes and blanks can also be obtained.
This item creates a signing document from the specified file on Box and sends a sign request.
An independent sub-process that can be invoked by various business flows. Through the Stripe API; 1) Stripe generates a Stripe invoice, and 2) Stripe sends the Stripe invoice. Billing will be done to customers who are already registered with Stripe, but when the customer is not registered, he or she will be billed after being created as a new customer.
The process records the results of a circular sent to dozens of target persons.
The number of persons to be circulated to can be varied.
The recipients can be specified in batches by a list of user email addresses or by targeting organisations.
This workflow receives HubSpot notification emails and manages customer outreach. The company name, customer name, etc., mentioned in the notification email are automatically stored as independent data. The results of the approach are also stored according to the sales activity.