Effektif User Guide. Release Tom Baeyens, Jan-Felix Schwarz, Philipp Giese, Peter Hilton, Chri

Transcription

1 Effektif User Guide Release 2.22 Tom Baeyens, Jan-Felix Schwarz, Philipp Giese, Peter Hilton, Chri

2

3 Inhaltsverzeichnis 1 Einleitung Einsatzmöglichkeiten für Effektif Vorteile How it works 3 3 Terminology Case Process case Ad-hoc case Task Process Action Trigger Role Organization Cases What is a case Create a case Create case tasks Completing a task Reopening a task Starting a process Process builder Triggers Actions Simple action list view Advanced flows view Variables Roles Action Types User task Send Google Drive file upload JavaScript action i

4 7 Control flow Transition Exclusive gateway Parallel Gateway Start event End event Data types Variables vs fields Salesforce Integration Effektif configuration Salesforce configuration Finish Effektif configuration ii

5 KAPITEL 1 Einleitung 1.1 Einsatzmöglichkeiten für Effektif Nutzen Sie Effektif um: Aufgaben und Übergaben zu koordinieren Freigaben durchzuführen Dokumente zu leiten Komplexe Geschäftsprozesse zu handhaben 1.2 Vorteile Was Sie bekommen: Kontrolle an den Stellen an denen sie gebraucht wird Flexibilität wo es möglich ist Weniger Verzögerungen (durch automatische Auslöser, Aktionen und Timer) Klare Kommunikation von Übergaben Nachverfolgbarkeit - wer hat was getan Klarheit - wer muss was tun Agilität - Prozesse können leichter geändert werden als Software 1

6 2 Kapitel 1. Einleitung

7 KAPITEL 2 How it works A process is a template for repetitive work. Processes are typically created by people who manage work and specify which tasks and actions have to be performed to reach a certain goal. For example: for every hire case, the tasks Conduct interview, Prepare contract and Create account have to be completed. After a process is published, many individual cases can be started. Effektif keeps track of which tasks and actions have to be performed for each case. Cases bring people together with relevant information that provides context for completing the tasks. Cases are also collaboration spaces where people can discuss and create new tasks for individual cases on the fly. 3

8 4 Kapitel 2. How it works

9 KAPITEL 3 Terminology 3.1 Case A case is a collaboration page for a particular goal. A case has subtasks representing the concrete action items to reach the goal. There are two types of cases: process cases and ad-hoc cases. Each case has an event stream that acts as an audit log and includes the information that is shared during collaboration, such as comments, documents and links. By using case comments instead of , participants ensure that discussions retain the full context for everyone involved. See Cases. 3.2 Process case A process case is a case that is associated with a defined process. The process describes what actions have to be done and in which order. In BPM terminology, a process case is also known as a process instance. 3.3 Ad-hoc case An ad-hoc case is a case without a predefined process. It s a collaboration space to reach any one-off goal. The case brings together a set of tasks, a discussion and documents, and allows participants to share any relevant context information for the tasks. 3.4 Task Tasks are concrete action items inside a case that can be assigned to people. In process cases, a task may have been created by a user task action. 3.5 Process A process is a template to automate repetitive work, like a recipe that describes the actions that have to be performed to achieve a goal. For example, consider a Hire employee process. Each time someone is hired, three tasks have to be completed: Conduct interview, Prepare contract and Create account. Each time the process is started, a new case is created. 5

10 3.6 Action Actions are the steps in a process that represent things to be done. When starting a process, Effektif will execute the actions in a process in the proper order. This ordering is also refered to as control flow and is specified with transitions, gateways and events. There are different types of actions: a user task will create a task in a case. A Send action will send an . A Google file upload action will upload a file to a Google Drive folder. 3.7 Trigger A trigger in a process specifies when the process is started. The manual trigger is the simplest, and starts the process when you start a new process case inside Effektif. The form trigger allows to specify a form that you have to complete to start a new process case. The trigger creates a new process case when it receives at its own address. There is no direct relation between triggers and start events. 3.8 Role A role is a mechanism used to assign user tasks in a process. Roles correspond to swimlanes in a BPMN diagram, and are also known as a process roles. Process roles are different from organizational roles. For example, there might be people your organization with the role Support engineer. However, each support case only has one person in the Support contact process role. A process role only lasts for the duration of a case, while organizational roles are more static and relate to the job you perform at the organization. See Roles. 3.9 Organization An organization represents a collection of Effektif users - typically a company - together with all their data in Effektif. The data in an organization is not visible to people outside the organization. When you re logged into Effektif, you see all the data inside one particular organization. If you re a member of multiple organizations, you can switch between organizations by selecting a different organization under your name in the top right corner. 6 Kapitel 3. Terminology

11 KAPITEL 4 Cases 4.1 What is a case A case is a essentially a small collaboration space for a particular goal. For example, Hire HR manager or Send quote to customer X. Cases are typically bigger then a simple task for a single person and smaller then a project. A case is used to break down the goal into concrete action items (or tasks) and to collaborate with others. The case is the central place where all relevant context information about the topic is shared and discussed. 4.2 Create a case To create a new case, navigate to Cases; on the Cases of menu, select Cases without a process, then click Start new case. Abbildung 4.1: Start a new task Then the case header appears. Abbildung 4.2: Enter case title Next, type the case title and hit Enter. The new case is now created. 7

12 Abbildung 4.3: New case 4.3 Create case tasks In a case, you can break down tasks like this. If you don t have tasks, the tasks section might have to opened like shown in this scenario: Abbildung 4.4: Type the title of the new task and hit Enter When a process is started, a case is created and all elements not having incoming transitions will be started. So if you only use the simple action list to create a list of user tasks, all those tasks in the list will be started immediate when the process starts. 8 Kapitel 4. Cases

13 4.4 Completing a task For ad hoc cases or tasks, there is a highlighted Done button to complete the task. When tasks have a form, the form is displayed in the same position and it has the button(s) to complete the task at the bottom of the form. Normally that will just be the Done-button, but in case of decisions, it can be multiple buttons. Each of those buttons will register the decision and complete the task in one go. Process cases have a process associated that knows when the case is completed. So usually those should not be completed manually. The Done button is deactivated out or there is a label saying Complete the tasks below. When the last action of a process completes the process case will be closed automatically. 4.5 Reopening a task When you see the Reopen button in a task, it means the task is completed. Reopening is good when you closed a task by accident or when you realize more needs to be done for this task. If you just forgot to attach a document or make a comment, you can still do that and you don t need to reopen the task for that. Reopening a task can be better then creating a new task because it has all the context in it. 4.6 Starting a process In the Advanced flows view, this means that start events are optional in most situations. But in situations like this, that can be confusing: Abbildung 4.5: Start event necessary Imagine we remove the start event, then there would be no elements without incoming transitions. Then the process would start and nothing happens Completing a task 9

14 10 Kapitel 4. Cases

15 KAPITEL 5 Process builder The process builder is used to create and configure executable processes. An executable process is similar to software, but it s easier to build automations using processes. With Effektif, non-technical people can create useful processes. 5.1 Triggers A trigger defines when a process is started. There is no relation between triggers and BPMN start events. See Start event Manual trigger A manual trigger is the simplest way to start a process. With a manual trigger, you start processes manually in Effektif, by selecting Start new case and then selecting the process to start Form trigger With a form trigger, you use a form to start a process. After selecting the form trigger, you can use the form builder to specify form fields Form documents Many organisations have existing processes that are based on forms, either on paper or in an electronic document. Often it s a good idea to just keep the form in its original format, such as a PDF document. You can use these documents as the basis for the process, rather then rebuilding the form in Effektif. If you have multi-page forms with complex layouts, then the original form might be the best option. People can then fill in the form, update the original document or scan a paper copy, and then upload the completed document to Effektif, using a single form field. Effektif can t read the data entered in form documents, so you will have to add fields to the form for pieces of information that impact the process flow. 11

16 trigger An trigger starts a new case for each that you send to the trigger s Effektif address. Note this is different from reading an existing account, such as your own. After selecting the trigger, you can see its address: Abbildung 5.1: Mail trigger configuration The trigger creates an variable that stores the that started the process. One way to use an trigger is to add the trigger address to a mailing list, such as support@example.com or info@example.com. You ll have to ask the administrator of the mailing list to add the process trigger s address to the list. Once you have done this, sent to the mailing list will also be forwarded to the process trigger address, starting the process in Effektif. You will then see the in the activity stream: Salesforce trigger A Salesforce trigger starts a new case in response to Salesforce sending an outbound message as part of a Salesforce workflow. Before you can use a Salesforce trigger, configure Salesforce Integration. When you have configured a Salesforce service, you can select it as a process trigger, so that messages from Salesforce will now trigger new cases. In the process definition, you can use the Salesforce object fields that are included in the Salesforce message just like normal variables. 5.2 Actions Actions are like steps in a process. An action might be a user task in Effektif, an operation on a file in a document management system or any other action that represents something to be done in a process. 12 Kapitel 5. Process builder

17 Abbildung 5.2: Trigger mail in stream Abbildung 5.3: Example of a Salesforce trigger 5.2. Actions 13

18 5.3 Simple action list view The simple action list view is the simplest way to create a process, as a list of actions. It s the easiest way to create checklist processes, which have a collection of user tasks that serve as a checklist. If you don t add any control flow in the Advanced flows view, all actions will be started immediately when the process starts. By default, all actions in the simple action list view run in parallel. 5.4 Advanced flows view The Advanced flows view is a BPMN diagram editor that shows actions and control flow elements like events and gateways. You use the Advanced flows view to add sequential flows between actions, decisions and other control flow behaviour Adding a transition You can create a transition in the Advanced flows view. A transition specifies sequential flow, which means the next action only starts when the previous one is complete. To add a transition, click to select the first action. Several symbols appear to the right of the selected element: Abbildung 5.4: Start creating a transition by dragging the transition symbol to the destination Click the transition symbol and drag it to the destination element. When you drag the symbol over the destination element, it indicates that you can drop to create the transition: Release the mouse button over the destination to create the transition Creating the next user task There is an easy way to create the next User Task in a process, similar to creating transitions above. Start by selecting the previous action: 14 Kapitel 5. Process builder

19 Abbildung 5.5: Creating a transition hovering over destination Abbildung 5.6: Start creating the next user task by dragging the action symbol 5.4. Advanced flows view 15

20 Click the rounded rectangle symbol and drag it to an empty place on the canvas. Abbildung 5.7: Drag the rounded rectangle symbol to an empty place Drop the symbol where you want to create the next user task. Release the mouse button to create new user task where you dropped it, with a transition from the previous action. Abbildung 5.8: Adding the next user task and its transition at the same time Alternatively, just click the user task icon to create a new user task in the default location, with a transition Control flow elements Control flow elements like events and gateways are also part of the diagram, but unlike actions, control flow elements don t represent something that should happen. Instead, you use events and gateways to specify the flow between the actions. 16 Kapitel 5. Process builder

21 5.5 Variables A process has variables that store workflow data when the process runs. All the information in forms and information required by the actions will be connected to these variables. Each case can stores its own values for each process variable. A process variable can contain a single value, such as a reference number, or containing multiple fields, such as an , which has fields like from, to, subject and attachments. 5.6 Roles A role (a.k.a. process role) is a kind of process variable that is used for assigning tasks. A role is a variable of type user that stores a single user You can optionally configure a role with a list of canidates. Roles are equivalent to swimlanes in BPMN. These process roles are not the same as organization roles. For example, you can be a team lead in your organization, which can be a position without an end date. A process role, such as Reviewer, has a different scope and only applies for the duration of a single case. You can use a role to assign multiple tasks a person from a group of candidates. For example, you might have a support process that includes three user tasks that are assigned to a support engineer. Instead, assign the three tasks to a new role called Support engineer, and add the relevant people as candidates for the role. Creating the first task that has a role will notify all of the candidates for the role. When one of the candidates takes the task, the subsequent tasks with the same role will be assigned to the same person. That s efficient because this person has the context knowledge about that case. If you reassign a task that has a role assignment, Effektif will update the role variable, and assign all subsequent tasks with the same role to the new assignee Variables 17

22 18 Kapitel 5. Process builder

23 KAPITEL 6 Action Types All actions are displayed as lines in the Simple action list and as rounded rectangles in the Advanced flows view. Actions typically have a configuration panel that opens up when you select the action. 6.1 User task A user task means a user has to perform a task. In the case, a task will be created. In the configuration form, following optional details can be specified: Assignment: A task can be assigned to a user or a process role Form: A task can be given a form. To complete the task, the form has to be submitted. Reminders: Reminder s and escalations. 6.2 Send The send action sends an to the specified user. In the configuration you can specify To: The people to which the is sent. You can type a plain address, select a variable, a variable field or a user in the organization. Subject: The subject of the . To use process data in the subject, start by typing a #. If the list of variable fields is too long, you can just keep typing after the # to narrow the list. In combination, use the up and down arrows to select the right field. Hit enter to select the field. To remove variable fields from the subject, just delete it like it s normal text. Attachments: To add attachments, click the attachments field. If there are files in the process variables, they will be shown. Select one of the file variable fields to add these as attachments to the mail. Body text: Just like in the subject, you can combine template text with variable fields to Start by typing a #. See Subject above in this list for more details instructions on using the #. 6.3 Google Drive file upload The Google Drive file upload sends one or more files to an account of your choice. After creating a Google Drive file upload action, the configuration panel shows a button to start configuring the account. 19

24 Abbildung 6.1: Initial configuration file upload When you click on the button Configure a Google Drive account, a popup window will appear that helps you setup authentication and integrate Effektif with your Google Drive account. The first screen shows what steps that will happen in the authentication popup window. After clicking Click to continue, the popup window will be redirected to Google. Google will perform a check if you re already logged in to Google in that browser. There are 3 possible outcomes: 1. If you re already authenticated with a single user to Google, the login screen is skipped and you go straight to the permission screen below. 2. If you re not yet authenticated to Google in this browser yet, you ll get a login window: 3. If you re authenticated with multiple users to Google in this browser, select the account you want to use. After authentication is complete, you ll see the following screen that allows you to give Effektif access to your Google account. After accepting the permissions, the pop up will disappear and the connection with your account is established. The Google Drive file upload configuration will now display the account and also show the folders in My Drive in your Google Drive account. Other people in your organization will be able to see that you have configured an account, but they will not be able to see youro address or browse your account folders. In the section Target folder you can now browse and select the folder you want to upload the file(s) to. In section Files to upload, you can select the variable field containing one or more files to be uploaded. If there was no file variable, a variable called File is created automatically. If there was already a file or list of files in the variables, it is preselected. 6.4 JavaScript action The JavaScript action allows developers to run a JavaScript to the process execution. After creating or selecting a JavaScript action, the configuration panel looks like this: The top section of the panel is the JavaScript text editor. By default, it already contains console.log( Hello World! );. The lower section allows you to test the script. Click Test it to execute the JavaScript code. The results are displayed underneath: 20 Kapitel 6. Action Types

25 Abbildung 6.2: Google Drive authentication flow 6.4. JavaScript action 21

26 Abbildung 6.3: Google Drive login 22 Kapitel 6. Action Types

27 Abbildung 6.4: Google Drive permission grant 6.4. JavaScript action 23

28 Abbildung 6.5: Google Drive authenticated configuration Abbildung 6.6: JavaScript configuration panel Abbildung 6.7: JavaScript test output 24 Kapitel 6. Action Types

29 Next, we ll show how to work with data. Suppose there is a form elsewhere in the process that has each type of field and looks like this: Abbildung 6.8: Form taking input for JavaScript When you open the JavaScript configuration again, you ll see the variables section shows some of the form field variables. Click Show all fields and select the variables you want to access in the script. In this example, all variables are selected. For each variable that is selected, you get an input field to specify a test value. Here you see all fields with a test value. To show you the data structures, we ve changed the JavaScript to print all variables. When clicking Test it again, we can see the JSON structure of the variable data for the different variable types JavaScript action 25

30 Abbildung 6.9: JavaScript variables Abbildung 6.10: JavaScript test values Abbildung 6.11: JavaScript script 26 Kapitel 6. Action Types

31 Abbildung 6.12: JavaScript JSON values 6.4. JavaScript action 27

32 28 Kapitel 6. Action Types

33 KAPITEL 7 Control flow You use transitions, gateways and events to specify the processing order of the actions in a process. 7.1 Transition A transition is an arrow from a source element to a destination element in the Advanced flows view. The transition specifies that the destination element is only executed after the source element is completed. A transition is called a sequence flow in BPMN. 7.2 Exclusive gateway Use an exclusive gateway to make a choice between multiple execution paths. The exclusive gateway selects one of the outgoing transitions, and only continues execution on that transition. There are two ways to configure an exclusive gateway: with a human decision or an 8automatic decision* Human decision Use a human decision for an exclusive gateway when a person must make a decision. The previous action must be a user task, which will include making the decision. The user interface presents the decision to the user as buttons on the user task form. Here s an example. Suppose you have a user task called Review contract, an exclusive gateway and the two user tasks Print contract and Update contract : Select the exclusive gateway. Human decision is the default type. After creating the elements and connecting them, as above, the exclusive gateway will be configured: To Print contract and To Update contract are the default decision buttons that will appear on the user task form. For each button, the label on the right indicates the next action in the process, which will be performed when the button is clicked. In this example, when the user clicks the decision button To Print contract, the Print contract task is executed and the Update contract task will not be executed. You can easily change the text on the buttons. For example, change them to Approve and Reject: After starting a new case for this process, the Review contract task will have decision buttons: When adding form fields to the task before the exclusive gateway - Review contract in this example - the decision buttons are added to the form. 29

34 Abbildung 7.1: An exclusive gateway must have at least one incoming and two outgoing transitions Abbildung 7.2: Default human decision configuration 30 Kapitel 7. Control flow

35 Abbildung 7.3: Customized decision buttons Abbildung 7.4: Task decision buttons 7.2. Exclusive gateway 31

36 7.2.2 Automatic decision An automatic decision is an exclusive gateway that selects an outgoing transition based on conditions that you choose. For each transition, you can formulate a condition using workflow data. Transition conditions are evaluated in order, from top to bottom. The workflow engine will take the transition with the first condition that is true, using the current case s field values. Abbildung 7.5: Automatic decision condition editor To specify a condition, start by selecting a field and a comparison operator. Enter either a static value in the input field on the right, or click the button to select another field. A condition can include multiple field value comparisons. To add more sub-conditions, click the button at the bottom of the list. You can also use the select field at the top to specify that either all conditions in the list must be true, or that it is enough for at least one of them to be true. When a sub-condition is incompletely specified, evaluating the whole condition will fail and the transition will not be taken. The symbol indicates an incomplete sub-condition, while the symbol indicates that the sub-condition is valid. Click either of these symbols to remove the sub condition from the list. An unspecified condition is marked with a symbol. Default transition An automatic decision usually has a default transition. A default transition is a fallback mechanism: if none of the conditions evaluate to true, the default transition is taken. To make a transition the default, select the per default item in the selection field at the top. 7.3 Parallel Gateway Use parallel gateways to model tasks that will be completed at the same time as each other, or one at a time but not in a particular order. To do this, you fork and join the sequence flow Forking With a parallel gateway, you can fork execution into multiple, concurrent flows. When process execution arrives in a parallel gateway, a new individual execution flow is created for each of the gateway s outgoing transitions. Let s look at the following purchase order example: 32 Kapitel 7. Control flow

37 Abbildung 7.6: The default transition Abbildung 7.7: A parallel gateway example 7.3. Parallel Gateway 33

38 In this example, the parallel gateway will be activated when the Enter purchase order user task is completed. The parallel gateway will create two individual paths of execution. One will take the transition to Receive payment and create that user task. Meanwhile, the other will create the Send goods user task. After Enter purchase order completes, both tasks Receive payment and Send goods will be created. You can have as many outgoing transitions as you want. All destination tasks for those transitions will be started at once Joining You also use a parallel gateway to join concurrent paths back together. In this case, the joining parallel gateway has more then one incoming transition. Workflow execution will wait at the gateway until as many execution flows arrive as it has incoming transitions. When the last concurrent flow arrives, the joining parallel gateway will activate and one execution flow will be created on the outgoing transition. To continue the previous example, extend the purchase order process to look: Abbildung 7.8: A parallel gateway example with join In this example, Archive purchase order will only start after both Receive payment and Send goods are complete Default forking By default, multiple outgoing transitions out of an action like a user task will be interpreted as parallel. Meaning that if you have multiple transitions out of a user task, all destination actions of those transitions will be performed concurrently. Let s look at a simple example. After Send goods completes, both tasks Receive payment and Send goods will be created immediate. You can combine default forking with a parallel gateway for joining Default merging When multiple transitions lead to a user task, the user task will be started for each execution flow that arrives there. This means that there is no implicit joining for parallel flows. 34 Kapitel 7. Control flow

39 Abbildung 7.9: Default forking Parallel gateway issues You will end up with problems if you loop back over parallel gateways. To avoid situations: Abbildung 7.10: Undesirable loopback and this: To avoid these issues, think of all actions between forking and joining as a self-contained part of the process, such that no transitions should cross that scope Parallel Gateway 35

40 Abbildung 7.11: Undesirable loopback 7.4 Start event A start event marks the start of a process. All process elements that do not have incoming transitions are considered start elements. Start events don t have a direct connection to triggers. You can usually leave out start events if you want to create more consice diagrams. 7.5 End event Like start events, end events are also optional. End events mark the end of an execution flow: Abbildung 7.12: End event This is equivalent to: 36 Kapitel 7. Control flow

41 Abbildung 7.13: No end event 7.5. End event 37

42 38 Kapitel 7. Control flow

43 KAPITEL 8 Data types The forms and some of the actions are linked to workflow data, called variables. Workflow variables are mostly created automatically, as when creating a new form field. Each variable has a data type. This section lists the data types variables can have. 8.1 Variables vs fields Workflow information is stored in variables. Each variable has a user-defined name and a type. A type can be a single value, like a string (text) or an address. Other types like user, file or are composite - consisting of several values. Composite types have a list of fields. When using expressions or configuring some action, references are made to workflow data. These can be references to variables, or to fields inside composite variables. The user interface guides you and shows the options you have String type The String type stores plain text File type The file type stores a file User type A variable of type user refers to a user in your organization. A user is an object type with the following properties: id (id) The unique identifier for this user firstname (string) The user s first name lastname (string) The user s last name address ( address) The address of the user address type The address type stores an address. 39

44 type The type stores an , and is used by the trigger. The that triggers the process will be stored as a variable. The data fields in the , such as from address or the attachments can be used later on. An is a composite type with the properties: id id: The unique identifier for this from ( address) The sender address to (list of address) The addresses of the recipients cc (list of address) addresses that receive a carbon copy of the message subject (string) The subject of the bodytext (string) The plain text message bodyhtml (string) The HTML code for an HTML (optional) attachments (list of file) The files to attach to the ID type The ID type is a special kind of string. These IDs identify objects and they are always created by Effektif, and have no other meaning. An example of an ID string is 53fae cea136ea Object types Object types are composite data types that have a list of fields. Each field has a name. For example: a user is an object type, with fields such as firstname, lastname, mailaddress. When an action requires data, like the files in a Google File Upload, it s possible to bind those input parameters to variables or fields inside variable objects List type A list is simply a collection of values. The list is ordered and all elements are of a specified type. 40 Kapitel 8. Data types

45 KAPITEL 9 Salesforce Integration Effektif integrates with Salesforce workflows. You can configure this so that changes in Salesforce will automatically trigger Effektif processes. 9.1 Effektif configuration Before you can set-up Salesforce integration, you need to create an endpoint in Effektif that Salesforce can send information to. Set this up in Effektif as follows. In the top-right user menu, select My Organisation and then select the Services tab. Under the Salesforce heading, enter a new trigger type name and select Create. Copy the generated Endpoint URL, or leave this window open for later. 9.2 Salesforce configuration Before you can enable Salesforce triggers, you need to configure Outbound messages, which are one kind of Salesforce workflow action. Set this up in Salesforce as follows. Select the Setup menu item, and select Build Create Workflow & Approvals Workflow Rules. Create or edit a new or existing workflow rule, and in the Workflow Actions section, select Edit. On the Specify Workflow Actions page, select Add Workflow Action and then New Outbound Message. On the Configure Outbound Message page, configure the new Outbound Message, to define which object fields to send to Effektif. In the Endpoint URL field, paste the Endpoint URL from the Effektif configuration you created earlier. 41

46 42 Kapitel 9. Salesforce Integration

47 Select Save. Do not forget to activate the workflow rule as soon as you have finished the configuration. To do this, click the Activate button at the top of the Workflow Rule Detail page. On the Outbound message page, next to Endpoint WSDL, select the Click for WSDL link, which opens a web service definition file. Save the workflowoutboundmessage.wsdl file, which you will use to configure Effektif, next. 9.3 Finish Effektif configuration The final configuration step is to use the web service definition file to configure the Salesforce service in Effektif. In the top-right user menu, select My Organisation, select the Services tab, and then select the Salesforce trigger type you created earlier. Select Upload document, and select the workflowoutboundmessage.wsdl file you saved earlier. Now you are ready to use the new Salesforce trigger in Effektif Finish Effektif configuration 43

48 44 Kapitel 9. Salesforce Integration