2. Design

Back Next

Start Properties

You can define the following Start properties for a process:

Property	Description
Binding	Select HTTP/SOAP or Event, depending on how the process is called. For example, to enable a JMS or AMQP process, choose Event. Default: HTTP/SOAP.
Allowed Groups	The groups that have access to the process service URL at run time. If the users in the group also have the Run privilege, they can invoke the process service URL. Use the Allowed Groups option when you want a group of users to have access to a service URL. For example, you have a group called 'Order Approvers'. If you enter Order Approvers in the Allowed Groups field, all users within the group have access to the service URL. The following image shows the Order Approvers group added to the Allowed Groups field: You can enter more than one group in the field. You can enter data in the Allowed Groups and the Allowed Users fields. If a user falls into either the Allowed Groups or the Allowed Users category, they will have access to the service URL. If you enter a role in the Allowed Groups or the Allowed Roles field, you cannot select Allow anonymous access and vice-versa. If you do not enter a role in the Allowed Roles field or do not select the Allow anonymous access option, no service URL is available for the process. You can, however, call the process as a subprocess. If you want the process to appear in the API Manager service, you must either select the Allow anonymous access option or use the Allowed Groups or the Allowed Roles field. For more information about managing APIs, see the API Manager documentation.
Allowed Users	The users that have access to the process service URL at run time. If the users also have the Run privilege, they can invoke the process service URL. Use the Allowed Roles field when you want a specific user to have access to the service URL. The following image shows the user jsmith in the Allowed Users field and the group Order Approvers in the Allowed Groups field: In this process, users in the Order Approvers group and the user jsmith have access to the service URL. You can enter more than one user in the field. If you enter a role in the Allowed Groups or the Allowed Roles field, you cannot select the Allow anonymous access option and vice-versa. If you do not enter a role in the Allowed Roles field or do not select the Allow anonymous access option, no service URL is available for the process. You can, however, call the process as a subprocess. If you want the process to appear in the API Manager service, you must either select the Allow anonymous access option or use the Allowed Groups or the Allowed Roles field. For more information about managing APIs, see the API Manager documentation.
Only accepts HTTP authorization requests from the API Gateway	Select this option to enable OAuth2 authentication for the process and configure the API to accept only HTTP authorization requests from the API Gateway. To invoke the API from the API Gateway, the following users must complete configuration tasks: API provider The API provider must perform the following tasks: Create a managed API for the process in API Manager and enable OAuth2 authentication for the managed API. Create an OAuth2 client in API Manager, and generate the client ID and client secret. Send the Informatica Intelligent Cloud Services OAuth 2.0 server URL and the client credentials to the API consumers. API consumers API consumers must perform the following tasks: Authenticate against the Informatica Intelligent Cloud Services OAuth 2.0 server and use the OAuth 2.0 client credentials to generate an OAuth 2.0 authorization token. Use the OAuth 2.0 authorization token to invoke the API. For more information about creating an OAuth2 client and invoking an API with OAuth2 authentication, see the API Manager help. You can use the Only accepts HTTP authorization requests from the API Gateway option only for processes that run on the Cloud Server. Processes that use the Only accepts HTTP authorization requests from the API Gateway option can also be scheduled and run with one or more process inputs.
Allow anonymous access	When selected, Process Designer lets anyone use the process. This means that access to the process is not tied to a specific role or to any credentials. If you select the Allow anonymous access option, you cannot enter a role in the Allowed Groups or the Allowed Users fields, and vice-versa. If you do not enter a role in the Allowed Groups or the Allowed Users field or do not select the Allow anonymous access option, no service URL is available for the process. You can, however, call the process as a subprocess. If you want the process to appear in the API Manager service, you must either select the Allow anonymous access option or use the Allowed Groups or Allowed Users fields. For more information about managing APIs, see the API Manager documentation.
Applies To	The type of object associated with the process. The objects that display in this list are the process objects you defined separately or generated in a defined connection. Drill down the list to see process objects and connections, and then select one of these items. Select a process object only if the process will be embedded in another process. To change the Applies To property of a published process, you must first unpublish the process. Then, change the Applies To property and republish the process There are two special values: Any : Choose Any if you do not want to associate the process with a specific object. When you select this option, the process does not automatically have access to an object's fields. Use this object type when a process creates a new object and does not access information within existing objects. Home (Salesforce) : Select Home if you want a process to be visible from Home or any initial location where users launch all processes, regardless of the object type. If you directly invoke a process, the Applies To setting must be either Any or a specific object in a service, but not a process object.
Run On	Use this list to specify where the process must run. You can select Cloud Server , a specific agent, or a Secure Agent group. If a process uses a connector that is event based, ensure that you run the process on the same agent that the connector runs on.
Run As (Salesforce only)	For Salesforce only, you can choose whether to run the process as the Current User or System . Choose Current User if the process should have the same privileges as the user who is running it. Choose System if the process should have system-level permissions to enable actions that the process user may not otherwise be able to access. For example, if a user does not have access to account objects, if the process is running as System, the process can still access the account objects to the extent needed to run the process.