Workflow Termination
Hi All,
I developed a Workflow.It has many parallel processes in it which are dynamic.This workflow triggers from a Custom Transaction when the enduser uses "SUBMIT' pushbutton on the screen.On my screen i have SUBMIT & CANCEL Pushbutton.After using SUBMIT Pushbutton workflow triggers.My question is, If the user wants to cancel the Workflow which is still in process, user presses the CANCEL Pusbbutton.But how should i handle it in Workflow, so as to cancel the Process which was started and it might be in progress(Bcoz its has many parallel processes, many user decision's have to be made).
Thanks,
Regards,
Srinivas.
Hello Srinivas,
According to my knowledge you cannot stop the workflow once it has started. That too in your case it is 'N' parallen workflows are running.
But you handle it in another way such that workflow will only when the user presses the SUBMIT button or else back to the screen when user presses CANCEL button.
Regs,
Venkat Ramanan N
Message was edited by: Venkat Ramanan Natarajan
Similar Messages
-
Workflow Termination when IDoc is changed
Hi all,
For some inbound IDocs (SRCLST and INFREC), a workflow is triggered in case of an error. This works very well, and the extended notifications are triggered as well (mail included).
However, in some cases, an IDoc in error is retreated automatically by a certain job and often, succesfully (data is locked or...). Nonetheless, the workflow item remains in the inbox and can only be closed by executing it and clicking on "End Process". Sometimes this leads to a number of notifications (mail) that are being sent even though the IDoc has already been treated successfully.
Is there any way to trigger the termination of these workflows when the IDoc status is changed? The standard tasks that I am using are TS40007912 (SRCLST) and TS40007911 (INFREC). I am fairly new to workflows, so any assistance would be greatly appreciated.
Thanks in advance,
Aerv.Hi Aerv,
(on the requirement in general)
I think that your requirement (terminate error workitems when Idoc is re-posted successfully) is part of standard:
Workitem termination is implemented by means of terminating events. If you look at 'terminating events' tab of task TS40007912( or TS40007911), you'll see that INPUTFINISHED event is there.
Thus, the workitem should terminate whenever INPUTFINISHED event fires.
The event fires when
- a user processed the idoc (see 'Error Handling Process' here Error Handling - ALE Programming Guide - SAP Library) ,
- the system processed the idoc successfully (RBDMANI2) - your case
(on your setup)
I suppose, you don't need to add entries in SWE2 to make a terminating event work.
If you have those extra entries now, try deactivating them - probably it will correct the inconsistent behaviour as we see on the screen shot. -
Workflow Termination Notification Question
I have a question regarding termination notification workflow. I am trying to create termination notifications for a server and I have to verify both worklist and email notification.
I have checked the Set Up HRMS > Common Definitions > Self Service->Workflow Configuration and Personnel administrator role is assigned for Terminate Employee workflow. Also, in PeopleTools > Security > Roles & Permissions I have an user assigned to this role.
In Worklist->Worklist, I only see the termination action created through Manager Self Service->Job and Personal Information->Terminate Employee and not the one using Workflow Administration->Job Information->Job Data. Also, no email is received.
Could you give me a hint regarding this problem?Does anyone out there at Microsoft have accurate answers to these questions?
Thanks!EM -
Demantra workflow termination from DB
Hello all,
Is there a way to terminate demantra workflows from the database?
thanks and regards
estiIf the workflow calls a Plsql procedure and if you see the connection to the database in the session manager using TOAD or any tool, then Yes.
Thanks
Giri Ponnumani
+1416.473.2795
[email protected] -
The user does not exist or is not unique - workflow problem
I am using Solution Starters Dynamic Management workflow on my Project Server 2010. I was working fine for a year now, but today all workflows were broken when someone tried to submit them to a next stage. "Workflow terminated. An error has occurred
in the workflow."
I tried debbuging the workflow and it seems to be OK, but the problem appears when it needs to assign tasks to the approvers (they are in the Approvers group). When I remove users from the group that represents approvers (and leave that group empty), it
works fine, so I am guessing that users (who need to approve the stage) are the problem. My administrators are saying that there were no updates or changes on AD machine.
I don't have problem with users in any of people picker fields or anywhere else on the site. I am using claims auth.
What could be the reason for this behavior??
These are main errors from the log:
Failed to persist workflow instance: 7dc2e035-cd02-4284-b851-a829e372a809 with error code: 5, instance data size: 29578, internal state: Running, processing id: 1e2211d2-ef7b-4416-90ef-ac041396c200 2f83db27-34da-4275-a42e-0625240af921
The user does not exist or is not unique.
WinWF Internal Error, terminating workflow Id# 7dc2e035-cd02-4284-b851-a829e372a809
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: additionalNodes at Microsoft.Office.Workflow.Actions.OfficeTask.ProcessTaskError(Object sender, EventArgs e)
at System.Workflow.ComponentModel.ActivityExecutorDelegateInfo`1.ActivityExecutorDelegateOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime) at System.Workflow.Runtime.Scheduler.Run()It appears that this isn't the problem with users, but it is a problem with Office Tasks. This is the main error in ULS logs (same as in the previous post):
"Specified argument was out of the range of valid values. Parameter name: additionalNodes"
I noticed that all content types are gone from my pwa site. Is it possible that my workflow is causing problems when adding tasks because somebody deleted all content types?? -
Error Occured when trying to progress through the workflow
Tried to move a project from one stage to the next in the workflow and an error popped up saying,
Workflow: Workflow Terminated
An error has occurred in the workflow.
Now when you open the project in PWA instead of seeing the image of the workflow there is a message that reads,
Stage Status image - There is no workflow status to communicate because the project is not yet created
Any thoughts....EPM Admin
Try restarting the workflow. If that doesn't work, then you need to provide a whole lot of details on how the workflow is built, what version you are running, was it working before etc.
CHeers!
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries -
Hi,
We have travel expense workflow. We are callingn function module to create a trip in custom code. This triggers a workflow.
Our workflow works in Dev system but doesnt set the status of the trip properly in Quality. I did a comparision by downloding xml files both in Dev and QA. I uplodaded the one from Dev to QA also when I upload it to QA it is giving some problems with one event(Workflow termination).
Where do I check to see y it is not setting the status properly. When I go to log swi1 it looks ok but I am not sure as I am new to work flow. Please help.
SMCheck the respective method that you are executing in your Wflow to set the status of the trip. You shouls analyse the Workflow Log and find out that respective task and step whether it is executing properly.
Thanks
Arghadip -
hi can any one tell me what is workflow? where is it used ? how a workflow is created in SAP XI
Work Flow
Unit 1: Organizational Structure
Use
In order for the workflow system to establish the relationship between the requester and their superior, you must create an organizational plan in the system.
For this tutorial, of course, this organizational plan does not have to be complete and valid across the enterprise. To keep the test as simple as possible initially, define an organizational plan that only contains one administrator and one head of department.
Assign both items to yourself. As a result, all work items will appear in your own Business Workplace. Later you will modify the organizational plan such that you will have to work through the scenario with two users.
Procedure
The organizational plan required for this tutorial consists, when complete, of one organizational unit (= "department"), which contains two positions: a head of department and an administrator.
Each position is described by one job and each position is assigned one user as holder. The head of department position is also designated as chief position of the organizational unit.
Of course, a "real" organizational plan is created by arranging several organizational units with their positions in a hierarchy. Usually several positions are described by one job.
For further information, refer to the documentation Organizational Plan.
The procedure in this unit is divided into four parts:
1. You create an organizational unit.
2. Enter necessary jobs as required.
3. You create a position for the head of department in the new organizational unit.
You define a position in three steps:
i. You create a position that is assigned your organizational unit.
ii. You assign a holder to the position.
iii. You assign a job to the position.
3. You create a position for the administrator in the organizational unit.
Creating an organizational unit
1. Choose Tools  SAP Business Workflow  Development Definition tools  Organizational Management  Organizational plan  Create (T.Code: PPOCW).
2. Confirm the validity period proposed in the dialog box Creating a Root Organizational Unit.
This takes you to the Create Organization and Staffing (Workflow) screen. This user interface is divided into four screen areas:
3. On the Basic Data tab in the details area, enter an abbreviation and a name in the Organizational unit input fields.
Abbreviation: <ini_sales>
Name: <OrgUnit: Sales (ini)>
4. Choose .
You can now create the position for a head of department and one administrator.
Create jobs
When enhancing an organizational unit, the necessary jobs are usually already available. For this tutorial however, you create the necessary jobs for head of department and administrator yourself.
1. Choose Edit  Create jobs.
You go to the dialog box Create jobs. The lower area contains a list of existing jobs and the upper area contains an input table in which you can create new jobs by entering abbreviations and names.
2. In the input table, enter an abbreviation and a name for each of the new jobs.
Job - head of department:
Object abbreviation: < ini_dhead_C >
Name: < job: head of department (ini) >
Job administrator:
Object abbreviation: < ini_admi_C >
Name: < job: administrator (ini) >
3. Choose .
Creating Position for Head of Department
1. Change to the overview area in the staff assignments of the organizational unit, in order to assign positions, jobs and holders. Choose the arrow on the right next to the and then the staff assignments (list).
2. Choose .
A new position is then created in the staff assignments and is displayed in a new line in the table. The position is vacant and no job is assigned to it.
3. Open the details view for the new position in the details area by double-clicking on the entry in the table.
4. On the Basic Data tab, enter a code and a description in the Position input fields. Overwrite the previous contents.
Abbreviation: < ini_dhead_S >
Description: < position: head of department ( ini ) >
Assigning a holder to the position
You now assign R/3 users to the positions. The staff assignments for your organizational unit are displayed and you see the vacant position in the table.
5. Select User in the search area and enter the search criteria in order to find your user names.
All of the user names that match your search criterion are listed in the selection screen.
6. Select your user name in the selection area and drag it to the Person/User column of the position in the overview area.
Confirm the message that the relationship period of the validity has been changed.
7. Set the Head of own organizational unit indicator in the details area.
Assigning a job to the position
Assign the job of the head of department you created earlier to the position.
8. Select Job in the search area and enter the search criteria in order to find the job of the head of department.
All jobs that match your search criterion are listed in the selection screen.
9. Select job: head of department ( ini) in the selection area and drag it to the Job column of the position in the overview area.
10. Choose .
The job is assigned the position. Check this by switching to the staff assignments of the organizational unit. Select the organizational unit in the overview area, choose the arrow on the right next to the and then the staff assignments (list). The newly created job is displayed in the job column.
Create position for administrator and assign holder and job
You are now in the staff assignments of the organizational unit.
1. Choose .
A new position is then created in the staff assignments and is displayed in a new line in the table. The position is vacant and no job is assigned to it.
2. On the Basic Data tab in the details area, enter an abbreviation and a name in the Position input fields. Overwrite the previous contents.
ID: <ini admiS >
Description: < position: administrator ( ini ) >
3. Choose .
4. Select User in the search area and enter the search criteria in order to find your user names.
5. Select your user name in the selection area and drag it to the Person/User column of the position in the overview area.
Confirm the message that the relationship period of the validity has been changed.
6. Select Job in the search area and enter the search criteria in order to find the job of the administrator.
7. Select job: administrator ( ini) in the selection area and drag it to the Job column of the position in the overview area.
8. Choose .
Result
Display your entire staffing schedule again and make sure that all the information listed is correct.
You can display a detailed view of jobs, users, and positions. Choose the relevant cell in the table by double-clicking it.
In the details view of a position or job, all of the assigned tasks are displayed on the Tasks tab.
You have now completed the first unit (defining the organizational plan). You can now start on the next unit. To exit processing of the organizational structure, choose Back.
Unit 2: Creating a Workflow
Use
To define the flow of the approval process in the system, you first create a multistep task workflow template.
For further information, refer to Definition of Multistep Tasks in the SAP Business Workflow documentation.
Procedure: Creating a workflow template
1. Choose Tools  Business Workflow  Development Definition Tools  Tasks/Task Groups  Create (T.Code PFTC_INS)
This takes you to the Task: Maintain screen.
2. In the Task type field, choose the Workflow template entry.
3. Choose .
The Workflow Template: Add screen is then displayed.
Entering the basic data for the workflow template
1. Enter an abbreviation (of your choice) and a name (of your choice) for the workflow template to be created.
Abbreviation: < ini _ws>
Name: <Workflow: notification of absence ( ini )>
2. Choose .
3. In the Create Object Directory Entry dialog box, choose Local object.
The system has now allocated an 8-digit number for your workflow template. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. This number together with the letters WS forms the workflow ID. Make a note of the ID so that you can later call the workflow more quickly.
Entering a workflow description
4. Go to the Description tab.
5. Choose the text type Task description and then .
The SAPscript text editor is then launched.
6. Enter a text that describes the task. You can use the following proposal:
<You can use this workflow to create a notification of absence. This will then be sent to your superior for review. You will be notified of the result of this review.
If your request is rejected, you can revise it and resubmit it for review or withdraw it completely.>
7. Choose to return to the workflow template and then save the workflow template.
Determining agents
To enable the workflow template to be started in dialog, the workflow template must be assigned to its possible agents.
8. Select Additional data Agent assignment  Maintain
The workflow template: agent assignment screen is displayed.
9. Position the cursor on the name of your workflow template.
10. Choose Properties
The dialog box Task: <Workflow: Notification of absence (ini)> is displayed.
11. Set the General task flag.
12. Choose Copy and then .
Designating your workflow template as a general task means that every user in the system is authorized to start this workflow template in dialog.
Result
You have now created a workflow template as a "framework" for a workflow definition.
To create a workflow definition, you need tasks that are used as steps in the workflow definition.
Additional information: Tasks
A task can either be a single-step task or a multistep task. In our example of the notification of absence, making the application and checking the application are single-step tasks. The entire procedure involved in processing a leave request consists of these (and other) single steps, and is therefore a multistep task.
In this tutorial, a single step task is generally described as a task. The difference between the task types is only explicitly explained if there is a risk of confusion over multistep tasks. The term workflow is used as the umbrella term for the workflow template (and thus the multistep task) and the workflow definition. More precise differentiation only takes place if there is a risk of confusion.
On a technical level, the main difference between single-step tasks and multistep tasks is that:
Every single-step task refers to an object method
Every multistep task refers to a workflow definition
A workflow definition is made up of a sequence of different steps (for example, all steps required to process a leave request).
Standard tasks and workflow templates are client-independent. Customer and workflow tasks are client-dependent. Customer and workflow tasks are no longer supported and are therefore no longer used in this tutorial.
An Activity is a possible step type in a workflow definition. An activity refers to a task. It references a task, which can be a single-step or multistep task (subworkflow).
For further information, refer to Tasks and Task Groups in the SAP Business Workflow documentation.
Unit 4: Defining and Inserting Task "Create Notification of Absence"
Use
The notification of absence is created in the first step of the workflow. You will also need a task that executes this function. You can create the task separately from the workflow definition or directly from the Workflow Builder. This unit describes how you create the task from the Workflow Builder.
For further information on creating an individual task, refer to Definition of Single-Step Tasks in the SAP Business Workflow documentation.
Prerequisites
This task is a single-step task and it references one object method. The object type used (FORMABSENC (notification of absence)) and the required method (Create) are already defined and implemented in the Business Object Repository.
You are in the Workflow Builder and the initial workflow definition is displayed.
Procedure
Creating an Activity as a Step in the Workflow Definition
Add a first step of the type Activity to the workflow definition.
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step and click.
By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
Defining a Task "Create Notification of Absence"
You now create a new task, with which a notification of absence can be created.
1. Choose the arrow on the right next to the and then Create task.
The Basic data tab in the Standard task: Create screen is then displayed.
Entering the basic data
2. Enter an abbreviation (of your choice) and a name (of your choice) for the standard task to be created.
Abbreviation: < ini _creat>
Name :<Create notification of absence (ini)>
Work item text
The work item text appears as an information text in the Business Workplace as soon as there is a work item for the step with this task.
3. Enter Create notification of absence in the Work item text field.
Object type and method
4. Enter an object type and a method:
Object type: FORMABSENC
Method: CREATE
You can also use the F4 input help to select the method. Additional indicators associated with this method are set automatically.
You can view the definition of the object type entered by double-clicking on it. Information about its components is provided.
5. Save your task as a local object.
The system has now allocated an 8-digit number for your task. This number is made up of the 3-digit prefix number (Customizing setting) and a 5-digit number taken from a number range. The identification of this task consists of TS and the eight digit number.
Determining agents
Selecting the possible agents for this task determines who is to be authorized to make leave requests. For this task, this should be all employees in your enterprise. Define the task as a general task.
1. Select Additional data Agent assignment  Maintain
This takes you to the Standard task: Maintain Agent Assignment screen.
2. Position the cursor on the name of your task.
3. Choose Properties
The dialog box Task: <Notification of absence (ini)> is displayed.
4. Set the General task indicator.
5. Choose Copy and then .
6. Exit the task definition with .
Interim result
You have now defined your first task in full. This task is used in the activity that you created in the Workflow Builder.
Completing Activity
The Define Container Elements and Binding dialog box is then displayed in which the system proposes a change to the workflow container and a binding definition.
Upper part of the dialog box: Proposal for new container elements in the workflow container.
The system proposes that you create a local container element in the workflow container, which can store the reference to the notification of absence created in this step. The element has the technical name AbsenceForm .
Lower part of dialog box: Proposed binding definition
The system proposes that you define a binding from the task container to the workflow container. This binding transports the reference to the generated object (i.e. the created notification of absence) from the task (from the WIObject_ID element in the task container) to the workflow (to the AbsenceForm element in the workflow container).
Further information on automatic binding definition proposals is available under Binding Definitions from the Workflow Container and Binding Definitions from the Task Container in the documentation on SAP Business Workflow.
1. Confirm the proposal with .
The new AbsenceForm container element is displayed in the workflow container. Local container elements are marked . The remaining elements in the workflow container are workflow system elements. For further information, please refer to Workflow System Elements in the Workflow Container.
2. Enter a text to describe the step.
You can, of course, leave the description of the task that is proposed by the system.
(The current step in your workflow definition appears here.)
3. Go to the Outcomes tab.
All of the outcomes for this step are displayed here.
4. Enter a text for the description.
The description (proposal: < Application filled out> ) in the Task executed synchronously line.
Each step has at least one subsequent event (in this case: Task executed synchronously). The description is the text with which the outcome is labeled in the workflow definition.
The Form does not exist and Form could not be generated outcomes are the possible exceptions that could occur in the method execution. You "run the risk" of not intercepting these exceptions and not modeling any exception handling in your workflow definition. If one of the exceptions actually occurs at runtime, the workflow will assume the error status.
Checking the binding definition (optional)
1. Go to the Control tab.
2. Choose Binding (present).
The WF Builder: Binding for Step <Create notification of absence> dialog box is then displayed.
o In the upper part of the screen, the binding defined from the workflow container to the task container is displayed. The system executes this binding before providing the task for execution.
This binding direction is not relevant for this step since no information is to be transported from the workflow to the task.
o In the lower part of the screen, the binding defined from the task container to the workflow container is displayed. This system executes this binding after the user has processed the task.
Here, the binding is WIObjectId. &ABSENCEFORM& has been automatically defined here by the system. This binding ensures that the reference to the notification of absence created is not only known in the single-step task, but also in the workflow.
You can view the contents of both containers by choosing Workflow container or Task container.
(The element of the task container WIObject_ID is called Notif. of absence .)
3. Choose .
You then return to the step definition.
Entering the agents responsible
On the tab page Control, choose the entry Workflow initiator (expression) in the area agent as the agent responsible.
The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
You start your executable workflow later manually. At this point in time, the system fills the workflow container element WFInitiator automatically with your user name.
The above assignment informs the workflow system that the first work item for creating the notification of absence should be addressed as the "starter" as the workflow.
You return to the screen Workflow definition: Create step: Activity
Concluding step definition
1. Choose to check the step definition.
2. Choose to exit the step definition.
3. Choose to view the entire workflow definition in the workflow area on the screen.
You will notice that your workflow definition now contains a new step (the activity just created). The undefined step is also still there.
4. Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
5. Exit the Workflow Builder.
Result
You have now completed this unit and can start the next unit.
Unit 3: Starting the Workflow Builder
Use
A workflow definition is created with the help of the Workflow Builder.
Prerequisites
You have now created a workflow template ( Unit 2: Creating a Workflow).
Procedure
Calling the Workflow Builder
1. Choose Tools  Business Workflow  Development  Definition Tools  Workflow Builder.
The Workflow Builder is then launched with the workflow definition that was processed last. If the Workflow Builder has not yet been called, then an initial workflow definition is displayed.
The Workflow Builder screen is divided into the following areas.
The workflow definition is displayed in the Workflow area on the screen. If the workflow is shown in display mode, the step type area is not displayed. For further information, refer to Workflow Builder in the SAP Business Workflow documentation.
2. Choose and enter the abbreviation of your workflow template (< WSeight digit number >) .
You can use the F4 input help. Enter the start of the abbreviation for your workflow (for example: < ini*> ) and choose All of the workflows that match are displayed. Select your workflow and choose .
Result
The workflow definition is displayed and if necessary can be processed. If the Workflow Builder is called for the first processing of a newly created initial workflow definition, the following graphic is displayed:
If the graphic displayed differs from that above, check the graphic settings in the Workflow Builder. Choose Extras  Options, and click the Graphic tab. Choose the Without event-driven process chains view.
The start of the workflow definition is indicated by Start Workflow. If the new workflow definition has been called from the definition of a multistep task for which triggering events are defined, these are represented by the symbol and their description.
The end of the workflow definition is indicated by Workflow terminated.
The area in which the new workflow definition can be added is indicated by an undefined step with an outcome. Steps are displayed in the form of symbols. The description of an outcome is illustrated in the standard view with an arrow.
This unit is now complete. In the following unit you create the first step in your workflow and define a task for this purpose at the same time.
Creating an Activity as a Step in the Workflow Definition
Add a first step of the type Activity to the workflow definition.
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step and click.
By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
Entering basic data for control
3. Enter the abbreviation ( TS<8-digit number> ) of the standard task Create Notification of Absence in the Task field and choose .
If you no longer know the full abbreviation, you can use different methods to search for it:
o Use the F4 input help to search via the object type and method of the single-step task.
This brings you to the Search and Find: Tasks dialog box.
On the tab page Obj. type and method, enter the object type FORMABSENC and the method CREATE .
Then double-click your single-step task in the list. You should recognize your single-step task from your initials in the abbreviation. Choose .
o Enter a character string in the abbreviation or description and choose .
A list of tasks is then displayed in which you can double-click the desired task.
Every activity, as a step in a workflow definition, refers to a task.
At this point, the unique reference to this task is entered. The identification is made up of an abbreviation (T, TS, WF, or WS) followed by an 8-digit number.
If you select a workflow task (WF) or workflow template (WS) as your task, your activity is a subworkflow. If you select a customer task (T) or standard task (TS), your activity is a single step.
The Define Container Elements and Binding dialog box is then displayed in which the system proposes a change to the workflow container and a binding definition.
o Upper part of the dialog box: Proposal for new container elements in the workflow container.
The system proposes that you create a local container element in the workflow container, which can store the reference to the notification of absence created in this step. The element has the technical name AbsenceForm .
o Lower part of dialog box: Proposed binding definition
The system proposes that you define a binding from the task container to the workflow container. This binding transports the reference to the generated object (i.e. the created notification of absence) from the task (from the WIObject_ID element in the task container) to the workflow (to the AbsenceForm element in the workflow container).
Further information on automatic binding definition proposals is available under Binding Definitions from the Workflow Container and Binding Definitions from the Task Container in the documentation on SAP Business Workflow.
4. Confirm the proposal with .
The new AbsenceForm container element is displayed in the object area of the workflow container folder. Local container elements are marked . The remaining elements in the workflow container are workflow system variables. For further information, please refer to Workflow System Variables in the Workflow Container.
5. Enter a text to describe the step.
You can, of course, leave the description of the single-step task that is proposed by the system.
(The current step in your workflow definition appears here.)
6. Go to the Events tab.
All of the outcomes for this step are displayed here.
7. Enter a text for the description.
The description (proposal: < Application filled out> ) in the Task executed synchronously line.
Each step has at least one subsequent event (in this case: Task executed synchronously). The description is the text with which the outcome is labeled in the workflow definition.
The Form does not exist and Form could not be generated outcomes are the possible exceptions that could occur in the method execution. You "run the risk" of not intercepting these exceptions and not modeling any exception handling in your workflow definition. If one of the exceptions actually occurs at runtime, the workflow will assume the error status.
Checking the binding definition (optional)
1. Go to the Control tab.
2. Choose Binding (present).
The WF Builder: Binding for Step <Create notification of absence> dialog box is then displayed.
o In the upper part of the screen, the binding defined from the workflow container to the task container is displayed. The system executes this binding before providing the task for execution.
This binding direction is not relevant for this step since no information is to be transported from the workflow to the task.
o In the lower part of the screen, the binding defined from the task container to the workflow container is displayed. This system executes this binding after the user has processed the task.
Here, the binding is WIObjectId. &ABSENCEFORM& has been automatically defined here by the system. This binding ensures that the reference to the notification of absence created is not only known in the single-step task, but also in the workflow.
You can view the contents of both containers by choosing Workflow container or Task container.
(The element of the task container WIObject_ID is called Notif. of absence .)
3. Choose .
You then return to the step definition.
Entering the agents responsible
Choose Workflow initiator (expression) under Agents.
The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
By doing so, you choose the agent responsible.
You start your executable workflow later manually. At this point in time, the system fills the workflow container element WFInitiator automatically with your user name.
The above assignment informs the workflow system that the first work item for creating the notification of absence should be addressed as the "starter" as the workflow.
You return to the screen Workflow definition: Create step: Activity
Concluding step definition
1. Choose to check the step definition.
2. Choose to exit the step definition.
3. Choose to view the entire workflow definition in the workflow area on the screen.
You will notice that your workflow definition now contains a new step (the activity just created). The undefined step is also still there.
4. Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
5. Exit the Workflow Builder.
Result
You have now completed this unit and can start the next unit.
Unit 5: First Test
Use
You are now going to start a workflow in dialog for the first time, which will run according to your workflow definition. This workflow definition only contains a step for creating a notification of absence so far.
For further information on starting workflows, refer to Starting Workflows (Test Environment) in the SAP Business Workflow documentation.
Prerequisites
The creation of a notification of absence, which you carry out within your workflow, is reported on a system-wide basis by an event. Other workflows entered as event receivers for this event may therefore be started. The notification of absence created by you (and published by the event) is then also processed with these workflows.
This event is not used in connection with this tutorial.
To ensure that only you work exclusively with the notification of absence, you can deactivate any existing linkages between the event and its receivers. Proceed as follows:
If you carry out the following steps, you prevent other workflows being started unintentionally by your notification of absence.
However, you may interrupt other workflow demonstrations. Therefore, be careful and speak to the colleagues involved if necessary.
1. Choose Tools  Business Workflow  Development  Utilities  Events  Simulate Event.
2. Enter FORMABSENC in the Object type field.
3. Enter created in the Event field.
4. Choose .
The system simulates the event FORMABSENC.Created and establishes which workflows would be started.
5. If you find one or more entries in the list under the branch Tasks without syntax errors to be started, position the cursor on an entry and choose Event linkage.
The dialog box Event linkage: Triggering events is displayed.
6. Position the cursor on the entry with the red background for the event and choose .
The linkage between workflow and event is deactivated.
7. Choose .
8. Repeat steps 5 to 7 or repeat the whole simulation as applicable.
Procedure
Starting the workflow and filling out the form
1. If you are still in the Workflow Builder, choose .
The Start Workflow (Test Environment) screen is then displayed. The number of your workflow template is entered.
If you are no longer in the Workflow Builder, choose Tools  Business Workflow  Development  Runtime Tools  Start Workflow (Test Environment). Enter the identification of your workflow or use the F4 input help.
2. Choose .
To handle work processes more quickly, SAP Business Workflow supports Advancing with Immediate Dialog. When a workflow is started in dialog, this means that the first work item of the workflow is made available for processing immediately provided that the user who starts the workflow is also one of the recipients of this first work item. This is the case here because you entered the container element WFInitiator as the agent in the step definition.
The Create notification of absence screen, therefore, is displayed immediately where you can see the notification of absence form. It is the method Create that is executed with the first work item.
3. Fill out the form with entries of your choice.
4. Choose .
The Start Workflow (Test Environment) screen is then displayed again.
5. Choose and exit the Workflow Builder if necessary.
Starting a workflow / Business Workplace
Before you extend your workflow definition, carry out the following test. It will familiarize you with the Business Workplace.
1. Start your workflow in dialog again. Choose Tools  Business Workflow  Development  Runtime Tools  Start Workflow. (T.Code SWUI)
You go to the screen Start task.
2. Choose your workflow in the table on the left.
3. Choose Start on the right-hand side of the screen.
The notification of absence form is displayed.
4. Do not make any entries and do not save. Instead, choose .
You have now started the workflow but canceled the processing of its first step. But the processing of the work item is not yet completed. You have only broken the processing chain of advancing with immediate dialog.
5. Choose .
6. Choose Tools  Business Workflow  Development  Runtime Tools  Business Workplace.
7. Open the Inbox node and choose the Workflow folder.
Your workflow inbox now contains (at least) one work item for processing. This is the work item for creating a notification of absence, the processing of which you canceled previously.
8. Select the work item, if necessary, and choose .
You return to the Create notification of absence screen where the notification of absence form is displayed.
9. Fill out the form and choose .
The work item disappears from your workflow inbox.
Result
You have now completed this unit and can start the next unit.
Reporting and analysis
In this first test, you will take a look at the work item analysis function.
1. Choose Tools  Business Workflow  Development  Reporting  Work Item Analysis  Work Items Per Task
The Work Items Per Task screen is then displayed.
2. Select the monitoring period Today.
3. Select the work item type (Sub-)Workflow only.
4. Choose .
The system then determines all of the workflows that were started today. These are then listed on the Work Items Per Task from <Date> to <Date> screen. The number of work items in each workflow is also shown here.
Make sure that you only ever analyze the work items for your workflow and your absence notification.
5. Display the list of associated work items by double-clicking the workflow ID.
Both the workflows you just started for this workflow identification are displayed with status Completed.
6. Display the workflow log by double-clicking a work item ID.
The Workflow Log screen is then displayed.
For information on the workflow log, see Workflow Log in the SAP Business Workflow documentation.
7. Exit the work item analysis function.
Unit 6: Creating a Task "Check Notification of Absence"
Use
You define the task Check notification of absence. This task is incorporated into your workflow definition as the second step.
As this is not the first task you have defined, many steps will doubtless be familiar to you. (Refer to Unit 4: Defining and Inserting Task "Create Notification of Absence.)
Prerequisites
The object type used (here: FORMABSENC (notification of absence)) and the required method (here: Approve) are already defined and implemented in the Business Object Repository.
Procedure
1. Choose Tools  Business Workflow  Development Definition Tools  Tasks/Task Groups  Create.
The screen Task: Maintain is displayed.
2. In the Task type field, choose the Standard task entry.
3. Choose .
The Basic data tab in the Standard task: Create screen is then displayed.
Entering the basic data
1. Enter an abbreviation (of your choice) and a name (of your choice) for the task to be created.
Abbreviation: < ini _check>
Name: <Check notification of absence (ini)>
Object type and method
2. Enter an object type and a method:
Object type: FORMABSENC
Method: APPROVE
You can also use the F4 input help to select the method.
Work item text
3. In the Work item text field, enter the text Check notification of absence from .
4. Choose . Save your standard task as a local object.
5. You can include variables in your work item text to be filled with values from the task container at runtime..
The name of the creator of the notification of absence is to be included into the work item text. As soon as the work item appears in the superiors Business Workplace, the name of the creator appears in the work item information text.
Position the cursor in the work item text after the word of .
6. Choose .
The Please choose an expression dialog box is then displayed.
7. Choose the expression Notif. of absence by double-clicking the Container node.  Issuer object ref.  Name.
If WIObject_ID is displayed instead of Notif. of absence, choose . The system then displays the description of the expressions instead of their technical names.
The variable &_WI_Object_ID.Creator.Name& has been added to the work item text automatically. The variable name displayed here is the technical name of the expression.
You can integrate all of the elements in the task container in your work item text. This enables you to include information into the work item text, which is not available until runtime.
Entering the description text
1. Go to the Description tab.
2. Choose Task description in the Test type field.
The current task description is then displayed. This text is intended to inform future recipients of a work item in which this task is referenced and help them in their work.
The text will often be similar to the work item text or may supplement it.
3. Choose .
4. Enter the following text:
Please check notification of absence no. &_WI_OBJECT_ID.NUMBER& from &_WI_OBJECT_ID.CREATEDATE& of employee &_WI_OBJECT_ID.CREATOR.NAME& .
Decide whether to approve the request.
If you want to insert an expression from the task container as a text variable, choose Include  Expression. Then choose the relevant expression in the Please choose an expression dialog box by double-clicking the Container node.
5. Choose .
6. Choose .
Determining possible agents
1. Select Additional data Agent assignment  Maintain
This takes you to the Standard task: Maintain Agent Assignment screen.
2. Position the cursor on the name of your task.
3. Choose .
You go to the dialog box Choose agent type.
4. Double-click Job.
The dialog box Choose Job is displayed.
5. Enter either part of or the full abbreviation of the job that you created for the head of department in Unit 1: Organizational Plan.
You return to the screen Standard task: Maintain agent assignment.
6. Choose .
You have linked the task to the job of a head of department. In the organizational plan, you use this job to describe a position. The holder of the position is also displayed.
7. Choose .
8. Choose .
Result
The task for checking the notification of absence is defined in full. You can now exit the screen for defining a task.
In the next unit, you will incorporate this task into the workflow definition.
Display your organizational plan again.
a. Choose Tools  Business Workflow  Development  Definition Tools  Organizational Management  Organizational Plan  Display.
b. Choose your organizational unit in the search area. Display it by double-clicking the entry in the table.
c. In the overview screen, choose the arrow on the right next to the and then Staff assignments (list).
d. Display a detailed view of the position of the head of department by double-clicking the entry in the list.
Here, you can see that this position is assigned to the job and, on the Tasks tab, that it is also assigned to the task Check notification of absence.
Unit 7: Including "Check Notification of Absence" in the Workflow Definition
Use
The task with which an employee can check a notification of absence is ready to be included into your workflow definition as the next step.
Prerequisites
You have defined a workflow with a step ( Unit 4: Task Defining and Inserting "Create Notification of Absence") and created the task Check Notification of Absence ( Unit 6: Create Task "Notification of Absence").
Procedure
Calling the Workflow Builder
1. Choose Tools  SAP Business Workflow  Development  Definition Tools  Workflow Builder.
The Workflow Builder is then launched in display mode with the workflow that was processed last.
2. Work through the following steps to display your workflow for this tutorial in change mode.
i. If the workflow you created for this tutorial is already displayed, choose . Go to step 3.
ii. If a different workflow is displayed, check whether the workflow you created is listed in the My available tasks area. Double-click it and choose . Go to step 3.
iii. Choose . Enter the complete abbreviation in the Task field on the Open other workflow definition dialog box and press RETURN. You can now also enter the workflow abbreviation. Enter either the full abbreviation or just the first characters (for example: < i*> ). Press F4 . The search result is then displayed. Choose your workflow by double-clicking it. When you enter the abbreviation in the Task field on the Open other workflow definition dialog box, all of the available versions are displayed. Since you have not created any versions, select version 0000 and choose . The workflow is then loaded in display mode. To switch to change mode, choose .
1. Choose to display the entire workflow in the workflow area on the screen.
Creating a container element in the workflow container
You need an additional container element in the workflow container to store the name of the user who will execute this step. This user name is to be used later in the notification text that is sent to the requester.
1. Choose the entry <Double-click to create> by double-clicking in the Workflow Container.
The dialog box for entering a container element is displayed.
2. Make the following entries:
Element: Approver
Name: Approver
Description: Approver of the absence request
Reference table: WFSYST
Reference field: AGENT
3. Choose .
You have now added a local container element to the workflow container, which is ready to take an agent name, based on its data type reference. However, you have not yet determined a value for this container element.
Creating an Activity as a Step in the Workflow Definition
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step that follows the outcome Request completed and click.
By doing so, you add an activity to your workflow definition. The step definition is shown in the right-hand part of the screen. You are on the tab page Control.
Entering basic data for control
3. In the Task field, enter the abbreviation ( TS<8-digit number> ) of the task Check Notification of Absence that you defined in the previous unit. Choose .
If you no longer know the full abbreviation, you can use different methods to search for it:
o Use the F4 input help to search via the object type and method of the task.
This brings you to the Search and Find: Tasks dialog box.
On the tab page Obj. type and method, enter the object type FORMABSENC and the method CREATE .
Then double-click your task in the list. You should recognize your task from your initials in the abbreviation. Choose .
o Enter a character string in the abbreviation or description and choose .
A list of tasks is then displayed in which you can double-click the desired task.
Every activity, as a step in a workflow definition, refers to a task.
At this point, the unique reference to this task is entered. The identification is made up of an abbreviation (T, TS, WF, or WS) followed by an 8-digit number.
If you select a workflow (WS or WS) as your task, your activity is a subworkflow. If you select a task (TS or T), your activity is a single step.
You go to a dialog box in which the system proposes binding from the workflow container to the task container.
Here, the object reference to the notification of absence is transported from the workflow container (container element AbsenceForm ) to the task container (to the container element WIObject_ID ).
1. Choose to confirm the proposal.
Extending the binding definition
Now define another binding via which the current agent of the work item (the superior) is stored in a container element of the workflow container.
2. Choose Binding (present).
The Binding for Step 'Check notification of absence' dialog box is then displayed. If the first column is entitled Element, choose to display the element description.
The system has created the following binding definition from the workflow container to the task container:
Notif. of absence &AbsenceForm&
This binding ensures that the correct notification of absence is checked in the task.
3. Choose .
All of the container elements in the task container are now displayed on the left-hand side. You can define a binding from these container elements to the workflow container.
4. Position the cursor in the lower half of the screen, in the empty input field beside the container element Actual agent and call the F4 input help.
5. Double-click Approver.
In addition to the bindings already existing, the following binding is now defined:
Actual Agent &Approver&
6. Choose .
Determining outcomes
The method APPROVE of the object type FORMABSENC, to which you refer in the standard task definition, is defined with a result. The three possible values of this result are offered on the tab page Outcomes as outcomes of this step:
Approved
rejected
New
The indicates that these outcomes have already been transferred to the workflow definition. The outcome New is not really appropriate at this point. At this stage of processing, the notification of absence cannot be "new" any more. It should therefore not be incorporated in the definition.
1. Click on the symbol in front of the outcome New.
The symbol changes to .
The outcome Processing obsolete is processed if the relevant work item is set to obsolete via a process control step. This functionality is not used in this tutorial.
The outcome Form not available results from the exception defined for the method APPROVE. You could include this outcome into the workflow definition and would then have to model appropriate subsequent steps. However, you do not model anything for the purposes of this tutorial and accept that your workflow will have an error at runtime if this exception is raised.
2. Choose .
Two branches are now inserted in your workflow definition for the two marked outcomes Approved and Rejected.
Inputs for the agent
If you are working through this tutorial alone, do not specify anything for responsibility at this point. If it is processed when the workflow is executed, therefore, this step will be "offered" for processing to all employees declared as possible agents of the single-step task Check notification of absence. This means all user whose positions are described with the job head of department.
In your organizational plan, there is only one users who is a possible agent -> you.
You have maintained the organizational plan with jobs, positions, and user assignments in Unit 1: Organizational Plan.
You have defined the single-step task "Check notification of absence" and have assigned the possible agents in Unit 6: Definition of the Standard Task "Check Notification of Absence".
Concluding step definition
Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
Result
You can subject your workflow definition to a second test.
Unit 8: Second Test
Use
You start your workflow in dialog and two steps are executed. The notification of absence is created in the first step and then checked in the second.
Procedure
Starting the workflow and filling out the form
1. If you are still in the Workflow Builder, choose .
The Start Workflow (Test Environment) screen is then displayed. The number of your workflow is entered.
If you are no longer in the Workflow Builder, choose Tools  Business Workflow  Development  Runtime Tools  Start Workflow (Test Environment). Enter the number of your workflow or use the F4 input help.
2. Choose .
You go to the screen Create Notification of Absence.
From the requesters perspective
When the workflow is started, the work item for creating the notification of absence is provided to you directly for processing. This is because of advancing with immediate dialog. You were introduced to this in the first test.
3. Fill out the form and choose .
From the head of department's perspective
You created the step for checking the notification of absence in your workflow definition without specifying the agents responsible. This means that all of the possible agents of the single-step task are recipients of the work item. Since you occupy the position of both requester and head of department, you are automatically and immediately presented with the work item for approving the application. This is again because of advancing with immediate dialog.
As the superior, you have several options:
Approve the request
Reject the request
Cancel processing of the request.
4. Choose to cancel processing.
The Start Workflow (Test Environment) screen is then displayed again.
Exit this dialog and, if necessary, the Workflow Builder.
Reporting and analysis: Workflow outbox
In the first test of your workflow, you were introduced at this point to work item analysis. Now, you will be introduced to the workflow outbox.
Amongst other things, the work items which you started in dialog along with date, time and current status are displayed in the workflow outbox.
1. Choose Tools  Business Workflow  Development  Runtime Tools  Business Workplace.
2. In the tree displayed, choose Outbox  Started workflows.
3. Choose the arrow on the right next to the and then Today only.
The work items for all the workflows you started today are then displayed. Note the statuses of the work items displayed in the Status column of the Business Workplace. Read the F1 help for the Status column.
4. Position the cursor on the work item for the workflow just started. This work item has the status in process.
From the current workflow data, you can see that the step Create notification of absence has been completed successfully, when that was, and who processed it. The work item has the status completed.
You can also see that the work item representing the task for checking the request still has status ready and can therefore still be seen in the superiors Business Workplace.
Business Workplace - check notification of absence
You now once again occupy the position of the superior who canceled processing earlier when the application was to be checked.
5. In the tree, choose Inbox  Workflow.
The work items for you to process are displayed with their work item texts and certain other attributes.
A preview of the selected work item is displayed below the list and contains the description of the work item.
6. Select the work item for checking the notification of absence and choose .
You go to the work item display. There you find amongst other things the description text, also with replaced text variables.
7. Choose to return to the Business Workplace.
8. Choose or start execution by double-clicking the entry.
9. Either reject or approve the request. You should start the workflow twice and test each variant.
To check whether the workflow was completed correctly, go to your workflow outbox. The procedure is described above.
Result
Your workflow definition has now been tested and you can continue with the next unit.
Unit 9: Adding a User Decision
Use
In the previous units, you created a workflow whose definition contains two activities. These activities are based on two standard tasks that you created.
In this unit, you will add a user decision to your workflow definition.
With the user decision, the requester can decide to revise and resubmit the notification of absence if the head of department rejects it.
For further information, refer to Maintaining a User Decision in the SAP Business Workflow documentation.
Procedure
You start the Workflow Builder and open your workflow definition in Change mode. Proceed as described in Unit 7: Including "Check Notification of Absence" in the Workflow Definition.
Creating a user decision as a step in the workflow definition
1. Choose under step type. The cursor changes shape.
2. Position the cursor on the Undefined step that follows the outcome Rejected and click.
By doing so, you add a user decision to your workflow definition. The step definition is shown in the right-hand part of the screen. The Decision tab is displayed.
Entering basic data for user decision
3. Enter Your request was rejected by &. Revise? in the Title field.
This text is used as the title for the alternative decisions when the workflow is executed. The variable & is a placeholder for a parameter that is filled from the task container at runtime.
4. Choose the F4 input help in the Parameter 1 field.
The Expression for first parameter of user decision dialog box is then displayed.
5. Choose the Approver container element by double-clicking it.
Entering alternative decisions
6. Define the alternative decisions. Enter the following texts:
Decision texts Name
Decision: Revise request? Revise
Decision: Withdraw request? Withdraw
7. The decision texts you enter here appear as decision options on the screen that can be processed by the requester after their leave request has been rejected.
8. The descriptions are the terms used to describe the outcomes in the workflow definition.
9. Entering the agents responsible
10. Choose Workflow initiator (expression) under Agents.
The system enters the expression &_WF_INITIATOR& in the Expression field and in the input field beside the checkbox.
Concluding step definition
1. Choose to check the step definition.
2. Choose to exit the step definition.
3. Choose to view the entire workflow definition in the workflow area on the screen.
You can see that your workflow definition contains a user decision in the rejected branch. This has two outcomes whose branches converge again in the rejected branch. Each new branch contains an undefined step.
4. Choose .
The workflow definition is checked, saved, and, provided it does not contain any errors, activated. The system displays a message if problems are encountered during the test.
Result
You can now subject your workflow definition to another test.
Unit 10: 3rd Test
Use
You start your workflow in dialog and three steps are executed: Two activities, for creating and checking a notification of absence, and one user decision.
Procedure
Starting the workflow and filling out the form, checking the notification of absence, user decision
1. If you are still in the Workflow Builder, choose .
The Start Workflow (Test Environment) screen is then displayed. The number of your workflow is entered.
If you are no longer in the Workflow Builder, choose Tools  SAP Business Workflow  Development  Runtime tools  Start workflow (test environment). Enter the number of your workflow or use the F4 input help.
2. Choose .
You go to the screen Create Notification of Absence.
From the requesters perspective
3. Fill out the form and choose .
When you save the form, you (as superior) can immediately approve or reject the application (reason: advancing with immediate dialog).
From the superiors perspective
4. Do not approve the application.
5. Choose .
If the request is not approved, the next step in the workflow definition is the user decision. The requester was entered as the agent for the step. The decision is therefore offered to you again as the requester (reason: advancing with immediate dialog).
From the requesters perspective
You are given three options:
Revise request?
Withdraw request?
Cancel
It is irrelevant which option you choose since you have not defined any follow-up steps. You should start the workflow several times and try out the different options. The complete process flow can be checked each time in the work item analysis or workflow outbox.
Unit 11: Define and Include "Revise Notification of Absence" in the Workflow Definition
Use
You will now add the activity Revise notification of absence to your workflow definition. You will create the necessary task within the -
Is there an ap for finding/deleting corrupt files on OS X 10.7?
I seem to have a corrupt file(s) which cause my MacBook Pro to freeze inexplicably (and randomly) upon start-up. I've been told that this is a symptom of having a corrupt file.
Is there an an for finding/deleting corrupt files on OS X 10.7?
I'm pretty much bound to my computer and simply don't have the time to go through it manually.
Thank you.This is an old post and I am not the person who posted the original query, but I ran your terminal diagnostic and am hoping you are still attending to this forum. I have a mid 2011 macbook Air 11", 256 GB SSD, 1.8 GHz Intel Core i7, 4 GB 1333 MHz DDR3, Mac OS X v. 10.7.5 Lion. I have had various problems in my user homefolder for a while. I have gone through quite a few other troubleshooting and fixing steps, the most extensive following a posting here "Step by Step to fix your mac" by ds store in the Apple forums. These steps helped a lot. I did remove some 3rd party software as part of this process.
My computer is running well in general now, but one thing that has been a recurring problem is problems with move/cut-paste. I researched this online and ACL's being present where they're not supposed to be seems to be an issue. I have used terminal commands to remove ACL's, used Onyx to repair user permissions, rebooted with command-r to reset password screen and reset user permissions. They all help, but then a some point later on the problem recurs. When I run repair disk permissions with either disk utility or onyx I always get this message:
Repairing permissions for “maggieairHD”
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
ACL found but not expected on “Users”
Repaired “Users”
Permissions repair complete
This ALWAYS comes up, even if I run it immediately after running it and haven't done anything else on the computer in between.
I created another user and did not have the same problems I was having at the time with some programs, although I haven't used it that much to be able to really compare. The home folder permissions repair in Onyx comes out the same in that user, though.
Here are my results from your diagnostic terminal commands:
Last login: Wed Dec 26 09:36:47 on console
Maggies-MacBook-Air:~ maggieair$ kextstat -kl | awk '!/com\.apple/ {print $6 $7}'
com.rim.driver.BlackBerryUSBDriverInt(0.0.68)
com.logmein.driver.LogMeInSoundDriver(1.0.0)
com.protech.NoSleep(1.3.1)
com.parallels.kext.prl_usb_connect(7.0
com.parallels.kext.prl_hypervisor(7.0
com.parallels.kext.prl_hid_hook(7.0
com.parallels.kext.prl_netbridge(7.0
com.parallels.kext.prl_vnic(7.0
Maggies-MacBook-Air:~ maggieair$ sudo launchctl list | sed 1d | awk '!/0x|com\.apple/ {print $3}'
Password:
com.parallels.vm.prl_naptd
org.x.privileged_startx
org.postfix.master
org.ntp.ntpd
org.cups.cupsd
com.vix.cron
com.sharpcast.xfsmond
com.parallels.desktop.launchdaemon
com.microsoft.office.licensing.helper
com.adobe.fpsaud
Maggies-MacBook-Air:~ maggieair$ launchctl list | sed 1d | awk '!/0x|com\.apple/ {print $3}'
org.x.startx
org.openbsd.ssh-agent
com.parallels.vm.prl_pcproxy
com.parallels.DesktopControlAgent
com.parallels.desktop.client.launch
com.maintain.CocktailSystemEvents
Maggies-MacBook-Air:~ maggieair$ ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Sta}* L*/Fonts 2> /dev/null
/Library/Address Book Plug-Ins:
RCFaxAB.bundle
/Library/Components:
/Library/Extensions:
/Library/Frameworks:
AEProfiling.framework
AERegistration.framework
Adobe AIR.framework
AquaticPrime.framework
AudioMixEngine.framework
HPSmartPrint.framework
NyxAudioAnalysis.framework
PluginManager.framework
RIM_VSP.framework
RimBlackBerryUSB.framework
iTunesLibrary.framework
/Library/Input Methods:
/Library/Internet Plug-Ins:
AdobePDFViewer.plugin
AdobePDFViewerNPAPI.plugin
Flash Player.plugin
Quartz Composer.webplugin
QuickTime Plugin.plugin
Silverlight.plugin
flashplayer.xpt
googletalkbrowserplugin.plugin
npgtpo3dautoplugin.plugin
nsIQTScriptablePlugin.xpt
/Library/Keyboard Layouts:
/Library/LaunchAgents:
com.maintain.CocktailPurgeInactiveMemory.plist
com.maintain.CocktailSystemEvents.plist
com.parallels.DesktopControlAgent.plist
com.parallels.desktop.launch.plist
com.parallels.vm.prl_pcproxy.plist
/Library/LaunchDaemons:
com.adobe.fpsaud.plist
com.apple.remotepairtool.plist
com.microsoft.office.licensing.helper.plist
com.parallels.desktop.launchdaemon.plist
com.sharpcast.xfsmond.plist
/Library/PreferencePanes:
Flash Player.prefPane
JavaControlPanel.prefpane
NoSleep.prefPane
/Library/PrivilegedHelperTools:
Google Drive Icon Helper
com.bresink.system.securityagent3
com.microsoft.office.licensing.helper
/Library/QuickLook:
ParallelsQL.qlgenerator
iWork.qlgenerator
/Library/QuickTime:
AppleIntermediateCodec.component
AppleMPEG2Codec.component
/Library/ScriptingAdditions:
MTL.osax
/Library/Services:
AScrEd • New Script for Frontmost Application.workflow
AScrEd • Open Application Scripting Dictionary.workflow
AScrEd • Open Dictionary of Frontmost Application.workflow
AScrEd • Open with AppleScript Editor.workflow
Audio • Encode to iTunes Format.workflow
Browse Movie Library.workflow
Browse Photo Library.workflow
Browse iTunes Library.workflow
Disk Item • Rename Selected Items.workflow
Disk Item • Set Spotlight Comments.workflow
Image • Add Metadata to JPEGs.workflow
Image • Change File Type.workflow
Image • Import into iPhoto.workflow
Image • Print Image Files.workflow
Image • Rotate Clockwise.workflow
Image • Rotate Counter-Clockwise.workflow
Launch Terminal.workflow
PDF • Encrypt File.workflow
PDF • Set Metadata.workflow
Terminal • Get Manual for Command.workflow
Terminal • Insert Current Finder Directory.workflow
Terminal • Insert Selected Finder Items.workflow
UNIX • Apply Command to Selected Items.workflow
UNIX • New Terminal Window to Insertion Location.workflow
iPhoto • Spotlight Search for Detected People.workflow
/Library/StartupItems:
Cocktail
/etc/mach_init.d:
/etc/mach_init_per_login_session.d:
/etc/mach_init_per_user.d:
Library/Address Book Plug-Ins:
.DS_Store
SkypeABDialer.bundle
SkypeABSMS.bundle
Library/Fonts:
Library/Input Methods:
.localized
Library/Internet Plug-Ins:
CitrixOnlineWebDeploymentPlugin.plugin
Google Earth Web Plug-in.plugin
WebEx64.plugin
Library/Keyboard Layouts:
Library/LaunchAgents:
com.apple.AddressBook.ScheduledSync.PHXCardDAVSource.7D3946E8-ADA6-4982-87CA-565 69B042BAC.plist
com.apple.FolderActions.enabled.plist
com.apple.FolderActions.folders.plist
com.google.keystone.agent.plist
com.macpaw.CleanMyMac.volumeWatcher.plist
Library/Mail/Bundles:
Library/PreferencePanes:
.DS_Store
Archives.prefPane
Library/Services:
.DS_Store
GraphicConverter.service
Sync with MacDropAny.workflow
Maggies-MacBook-Air:~ maggieair$ osascript -e 'tell application "System Events" to get the name of every login item'
NoSleep, iTunesHelper, Caffeine, Dropbox
Maggies-MacBook-Air:~ maggieair$
I have removed NoSleep, Caffeine, itunesHelper and Dropbox from login items before and didn't notice any difference, so I put them back. Some of these I know I don't want, like rim/blackberry, adobe AIR. Skype has never worked consistently on this computer. I don't use most of these Services, and I know I had trouble with some that were not compatible with Lion before. I am not using Parallels much now, have been thinking about taking it off as it uses a chunk of my SSD. But I don't feel confident about getting rid of .frameworks etc safely.
I am glad to remove anything I don't use if I know how to do it safely. I am willing to remove anything I do use if it's necessary, but obviously would prefer to find a way to keep things that I find helpful.
I appreciate any suggestions! -
Workflow Manager 1.0 (SharePoint 2013): The process was terminated due to an unhandled exception
I am seeing large numbers of the following errors appearing in the event log of the SharePoint 2013 application server hosting Workflow Manager 1.0:
Log Name: Application
Source: Application Error
Date: [Date/Time]
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: [Application Server]
Description:
Faulting application name: Microsoft.Workflow.ServiceHost.exe, version: 1.0.20922.0, time stamp: 0x505e1b24
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c Faulting process id: 0x691c Faulting application start time: 0x01cfc2776b3f0d74
Faulting application path: C:\Program Files\Workflow Manager\1.0\Workflow\Artifacts\Microsoft.Workflow.ServiceHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id: b8157bf8-2e6a-11e4-9413-00155d38891d Faulting package full name:
Faulting package-relative application ID: Event Xml:
Log Name: Application
Source: .NET Runtime
Date: [date/time]
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [same application server]
Description:
Application: Microsoft.Workflow.ServiceHost.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception
Info: Microsoft.Workflow.Common.FatalException Stack: at Microsoft.Workflow.Common.Fx+<>c__DisplayClass2.<failfast>b__0() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object,
Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Event Xml:
Log Name: System
Source: Service Control Manager
Date: [date/time]
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Same application server]
Description:
The Workflow Manager Backend service terminated unexpectedly. It has done this 895 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.
Event Xml:
The SharePoint 2013 farm is updated through the September 2014 PU (KB2995902). Topology: 1 App, 2 WFEs. Workflow Manager 1.0 installed to the App server. Workflow Manager 1.0 cumulative updates one
and two have not been installed. The Service Bus Gateway and Service Bus Message Broker services are started. The Workflow Manager Backend service can be started, but then quickly stops.
Thoughts? Resolution? I would be grateful for any assistance.Hi Stephan,
As I understand, you are encountering the issue that Workflow Manager Backend service terminating each time. May I know did you run the update cmdlets after you installed the updates for SharePoint server 2013? Please confirm it per the link below:
http://technet.microsoft.com/en-us/library/dn133867.aspx
If you haven’t run the updates cmdlets, I suspect this is an install issue. I’d suggest you re-install workflow manager to resolve the issue:
1) Leave WFM/SB Farm
2) Uninstall updates and application in the following order and one at a time:
Service Bus CU1
Workflow Manager CU1
Service Bus 1.0
Workflow Manager 1.0
Workflow Manager Client 1.0
Microsoft Windows Fabric
3) Log into SQL server and delete Service Bus and Workflow Manager databases.
SBManagementDB
SBGatewayDB
SBMessageContainer01
WFManagementDB
WFInstanceManagementDB
WFResourceManagementDB
4) Install in the following order one at a time through Web Platforms Installer:
Workflow Manager 1.0
Service Bus 1.0 CU1
Workflow Manager 1.0 CU1
Regards,
Rebecca Tu
TechNet Community Support -
Termination workflow - (WS18900010)
Hi experts,
the functional team were busy with the configuration sap standard workflow for termination forms and processes and setting it up. although the workflow was activated it goes into the following errors. can i get hel for this workflow erors as i have been struggling to get it right but with no success..Workflow - (WS18900010) It is not running at all. but what i did is when i remove the rule 17900012 and the program exists (CL_HRASR00_POBJ_WF_EXIT) it starts the process then fails. i am still new as far as workflow is concerned.your help will be highly rewarded..
1. Transaction brackets of the workflow has been damaged
2. Error when starting work item 000030505067
3. Error when processing node '0000000547' (ParForEach index 000000)
4. Error when creating a component of type 'Step'
5. Error when creating a work item
6. Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event BEF_CREAT and (target) status : Excep
7. The process object GUID 8C76A34C25D3BE2AE10000000A080B1B is inconsistent
8. Notification of completion cannot be generated
9. Problems occurred when generating a mail
10. Error '9' when calling service 'SO_OBJECT_SEND'
11. Work item 000030505067: Object FLOWITEM method EXECUTE cannot be executed
Thanks in advance,
Thembass.
Moderator Message: Offering to rewards answers is against forum rules. Thread locked
Edited by: Neil Gardiner on Oct 1, 2010 2:22 PMHi
Thanks for your inputs.
We are on ECC5.0 and we are not implementing ESS/MSS.
I am wondering for implementing this workflow if we need to develop the screens, business objects, workflow every thing custon from scratch or do we have any thing standard where we can start from.
Appreciate your help.
Thanks
Srinivas -
Purchase Order Workflow - dialog step not receiving terminating event
Hi,
We have a scenario wherein based on the release groups and release strategies, different peope need to release the PO's.
I have been able to develop the workflow for this successfully, but here is where I am facing an issue.
After the PO has been created, based on the release group and strategy, it gets routed to the appropriate 1st approver. On their approval, the PO gets routed to the 2nd approver. Once the 2nd approver approves, the dialog step doesnt get completed and is still waiting for the terminating event. Event trace shows that the event is getting published, but there is no workitem to receive the terminating event. I am not sure why this is occuring for only 2nd approver onwards whereas for the 1st approver, the terminating event is received by the workitem.
I am using start conditions for my workflow to ensure only 1 instance of the workflow is triggered for a rel groups and rel strategy and release code, else I am multiple instances each time an approver approves the PO. I am not sure if the start conditions are causing this issue with the terminating events not being received with the workitems.
Any assistance is welcome.
Thank you,
SatishFrom the information provoided it seems you are using PO that is subjected to Release of PO for multiple Release Code and each Release Code Release is being done by one approver. If that is the case then I think the Terminating event should get caught. Please check whether the Terminating event that is getting triggered is specific to the Release Code or not.
Thanks
Arghadip -
Workflow- Adding Terminating event into a Decision Step
Hi
I have a requirement like, in the decision step for example 'Approve' or 'Reject' has to be executed from the web application by triggering a terminating event for this decision step. I have copied the decision BO DECISION to ZDECISION and created two terminating events and make it ashynchrounous. But this step is not getting executed in the workflow showing error as 'no terminating event is attached to the task'.
Any input on this is welcome. If you could reply bit early as I need the information ASAP.
Thanks in advance.
PadmanHi Padman,
Weclome to the SDN forums. We don't have a specific Workflow forum yet. Please post your questions in the General SDN Forum until we do.
I moved your questions there.
Thanks, Mark. -
We have a number of Sharepoint 2013 workflows running on various lists.
I want to create a simple page and drop in web parts that contain views of the lists, filtered on the workflow INTERNAL status.
This way I can see if any are currently suspended or terminated due to an issue and then resolve it quickly. At the moment I am going into each list item -> clicking on the workflow status and then seeing if the internal status is suspended, completed
or In Progress.
When creating a list view, the workflow status is not even an option in the "Filter On" dropdown , it does appear in the grouping option though.
I understand that if I could select the workflow status as a filter, I need to use the id of the status ie 5 = Completed.
But I cannot understand why my workflow status coloumn isnt a filterable option for me.
Any help would be appreciated.Hi
This works for 2010 and hope wont be different for 2013
The name of the workflow should be an option in the "Filter On" dropdown and equals to one of the below codes.
NotStarted = 0
FailedOnStart = 1
InProgress = 2
ErrorOccurred = 3
StoppedByUser = 4
Completed = 5
FailedOnStartRetrying = 6
ErrorOccurredRetrying = 7
ViewQueryOverflow = 8
Canceled = 15
Approved = 16
Rejected = 17 -
Workflow runtime error because of terminating event
Hi all,
In one of the workflow template, in one step, the Standard Task is having Terminating Event.
At the runtime, at the particular step, when it was in process, the terminating event is triggered. The step got completed,
But the workflow is not proceeding.
When I viewed the workflow log, In the perticular step after receiving the terminating event, the follwoing error is shown
" Workitem XXXXXX is locked by the user YYY(Enqueue error)".
The workitem number mentioned in the error is parent workitem number, not one of the particular step.
I know that there is a setting in SWU3 to schedule a job for errored out workitems. That job is already scheduled and it has tried two times and it stopped.
Now do I have to restart the workflow again or the issue can be resolved in the workitem in progress.
Thanks,
Sarayoodharan.Kthe terminating event is triggered. The step got completed,
But the workflow is not proceeding.
When I viewed the workflow log, In the perticular step after receiving the terminating event, the follwoing error is shown
" Workitem XXXXXX is locked by the user YYY(Enqueue error)".
Can you please let us know how you are trying to trigger the terminating event,I mean are you trying to trigger the terminating Programatically, then you might be using a FM to rasie the terminating event, by looking at the error it is clear that the event is triggered and the workitem got completed but the lock on the workitem is not released , you can release it by using the COMMIT WORK statement
You have to write the commit work statement after raising the even or make sure that someor the other way the commit work is executed, this is beacuse once the commit work statement is executed all Locks are released..
Maybe you are looking for
-
Highlighting TEXT - not the field - and clearing the set value for a new one
I have a form in which various text fields are set with a message to inform the user as to what kind of information I want typed in. My goals are: 1. Have the text get highlighted so when the user starts typing, the "old" value gets replaced with the
-
Function Module giving pruchase requisition release code ?
Hi everyone !! I am using the FM BAPI_REQUISITION_RELEASE_GEN in order to realease a purchase requisition, this works well as I give it a hard-coded value for input parameter REL_CODE. However in our company an intricate set of release strategies imp
-
My wife last night used Quicktime pro to make a audio recording of a book she uses in her classroom. But when we tried to play in on a CD player nothing was heard. Any ideas?
-
Why can i not open "show stationery" in mail
Hello, in my mail i cannot use „show stationery" anymore. If i click on ''show stationery'' in a new massage, the connection with my mail will be broken. Recently i tried to save a photo in: ''save as stationery''and than i have had this problem .
-
PDF to Excel- internal data errors
We have Acrobat XI and we converted a PDF document to Excel. It looked like it worked properly. However, we discovered when trying to sort the date field, that some of the dates became corrupted in Excel . It affected the stored values of the dates