Settings Required When Importing an Archive

The Apps published on the Questetra website are created with fictional Users, Organizations, etc. When you import an App from an archive you should change the settings according to the information on the workflow platform.

In addition, App settings errors are displayed in the workflow diagram on the App Details screen. You should check the error contents and modify all errors on the [Edit] screen, or you will not be able to [Release] the App.

Reference: Exporting Workflow App Definitions (App Archive QAR)

Settings on Import

Specify an archive file or the archive download URL, and click [Import] to display the import screen. You should set the properties of the App and the Swimlane allocation settings. In the Swimlane configuration you should link the User/Organization/Role information registered in your workflow platform to the Swimlane

• Check if the Users or Organizations (departments) assigned to the Swimlane are as you intended
  • Link the most appropriate User or Organization to the Swimlane (you can change the settings later)
  • Enter a partial name for the User or Organization. You can also click the icon on the far right which displays [Select from Organization Tree] to select
    • The name of the Swimlane does not always match the Organization name in your workflow platform
  • Be sure to specify required settings if they are blank
    • Manual: M303: Add [Organization] Units to Group User Accounts
• If a Swimlane is configured using a Role, setting is required
  • Enter the partial name of the Role to select
  • Import does not proceed if there are no Roles specified
    • Click [App List] on the left menu to stop the import
    • Go to [System Settings] > [Role List] and create the necessary Roles, then import the App from scratch
      • Manual: M304: Add [Role] Units to Group User Accounts

Settings error after Import

If the import is successful, you will enter the App Details screen. An error is displayed in the workflow diagram at the bottom of the screen if there is a deficiency in the settings. By clicking [Edit] you can correct all the errors. We describe the countermeasures for each setting type below.

HTTP Authorization Setting

 

• Add-ons and Service Tasks that use Basic Authentication or OAuth authentication require HTTP Authentication setting name to be specified
  • You need to add an authentication setting and give it a name
  • See the following page for more information about the OAuth configuration steps
    • Blog: How to Set OAuth2 When Utilizing REST API

Users who connect to Google

 

• Specify the User who has the administrator authorization for the target file or folder
• System-wide settings and User account settings are also required
  • For more information, you can see Utilizing Google Drive from Workflow – Sending files to people outside the company

Users who update the Options Master

 

• Click the [Me] button to specify the editor (you)
  • If the specified User does not have System Administration Authorization an error occurs when running the system
  • You should grant System Administration Authorization to the specified User or the system must be edited (modified) by the granted User
    • Manual: M301: Grant Administrator Privilege of the Whole System

App-Shared Add-on

• When using the Options Master () , Base PDF, or Service Task definition files () as App- Shared Add-ons in the workflow platform, an error will occur if the specified file is not registered
• Go to [App-shared Add-on] in the [System Settings] to register the necessary files, and edit the App settings again
  • Manual: M319: Register an Options-XML file to which the Process Model Definitions Refer
• Mainly used Add-ons (Download Page)
  • Zip Code Japan（Unavailable in Trial Edition ）

"Not available under the current license"

• Includes features available only in higher editions
• Delete the modelling element (BPMN Icons) and reconnect the arrow-shaped Flows, or delete the script contained in the Description of the Data Item

Other Important Notes

Although no errors will be displayed, you should check the following points before releasing (and activating) the App; in particular, you should check the operation and display contents thoroughly via testing functions such as [Debug process execution] before using the App for actual business.
Reference: How to Ensure Apps Operate Correctly

Initial value (Signatures and fixed sentences)

• Initial values may be set in Data Items
• Use [Form Preview] to check and rewrite the appropriate content
  • Manual: M207: Setting Initial Values of Data Items

A specified external file, such as Google Sheets

• You should change the file for reference if you specify [Get choice list via HTTP] in the Select-type Data Item

Update Data

• Check the data to be updated
  • Manual: M227: Auto Executing Data Binding, Arithmetic Operations

Mail Settings (fixed value)

• Rewrite the fixed values such as signatures entered in the Body and To fields of a [Throwing Message Intermediate Event (email)]
• Scroll to see the entire details
  • Tutorial: Let’s Send an Email Automatically in the Middle of a Workflow (Basic chapter)

HTTP Connection

• You should set HTTP according to the information of the event to which the [Throwing Message Intermediate Event (HTTP)] is connected
  • Manual: M225: Auto Sending of HTTP Requests with Business Data Inserted
• If connecting to a [Message Start Event (HTTP)] on the same workflow platform, replacing the [Throwing Message Intermediate Event (HTTP)] with a [Service Task (HTTP Request to Start Event)] in the same workflow platform will simplify configuration
  • BPMN Icon: Service Task (HTTP Request to Start Event)

Base PDF (Add-on)

• Please edit the Base PDF form file when using it for actual business, mainly the company name (signature) (Acrobat required)
  • Manual: M228: Auto Generating a PDF File with Business Data Inserted