Setting work item as obsolete

Hi Experts,
We are using modeled deadline monitoring. We are setting the " Workitem to obsolete" in the process control step.
Does this imply that the approver will not be able to execute the work item once it crosses it deadline.
In case of repeated deadline monitoring, what do we need to do.
Could you kindly guide us on the same.
Cheers,
Belinda Clarke

Hi Gautam,
Thanks for your response.
You have specified Loop using status change in the second branch.....what i wanted to know whether is it necessary to validate whether the work item was processed in the second branch.
Correct me if i am wrong....the concept of using a FORK is to have 2 activities running in parallel. Let us say that we have the first branch having the approval process and the second branch is having the loop using status change.
In the second branch, if we create a DUMMY method and set a deadline to it as 1 day. Let us set a container variable say lv_deadline as 'X' in the DUMMY method. Below that we put in a send mail step that sends the mail to the approver. This happens inside a loop in which we set the condition as Loop until lv_deadline = X.
Now in the case of FORK, these two activities will be running in parallel. The second branch will run after 1 day. If the work item is processed in the first branch, the control will go to the step after the FORK.
Is my understanding correct....do we need to validate in the second branch whether the work item was processed.
Kindly advice.
Regards,
Belinda Clarke

Similar Messages

Workflow - marking work items as obsolete

I'm working on a workflow that allows cost center managers to approve or reject purchase requisitions. I'm trying to create some logic that will trigger the workflow when the purchase req is significantly changed, in addition to just being created. When it gets changed, I want to be sure that it's not deleted. If it was deleted rather than being changed some other way, I want to mark all active work items for that particular req as obsolete so they're no longer out there for approval. I put in a "set obsolete" step for each piece of the workflow that creates a work item prior to terminating the workflow. When I try to test this, however, the workflow DOES recognize that the req was deleted, but it doesn't even show the "set obsolete" steps in the log, it just terminates. The "set obsolete" step doesn't seem to have much to it, but is it possible that I'm just doing something wrong?
Thanks,
Eric

Hi Eric
You shouldn't use "set obsolete" for this.
Depending on your version, you can either use a fork and a wait for the event "Deleted" in one of the branches or simply, in the new version, define a terminating event on the header level.
Check this thread, it explains how, the example is based on restart, but you can use the methodology to cancel you workflow instances as well.
Re: Restart Workflow ?
Regards
Morten Nielsen

Setting work Item as blocked

Hi,
We are using visual studio 2013.
We do use swimlines for work items.
If a work Item is blocked I set it to "blocked: Yes"
so far so good.
BUT I want a blocked Item to change colour in the board to "red" so it is easy to pick up during our daily standups.
I am gusseing I can set up a Query to find any work Items that are blocked, but it would be better if it was a way make the blocked ones to appear different than others on the board (like in Jira)

Hi Haavard,
currently this is not possible to change the appearance on the board. The PG knows that Problem and they are working on it.
Take a look at the new Features for TFS 2015
http://blogs.msdn.com/b/visualstudioalm/archive/2015/01/21/agile-project-management-futures.aspx
It will be possible to Change the appearance of the Cards on the board.
If you can´t live without that the only solution is the
Taskboard Enhancer Plugin but this is only a hack (reverse Engineering) and is not a supported solution.
Regards,
Daniel

Terminating the work item

Hi,
I have an requirement where in i need to terminate the workitem after a user decision step. The termination should happen when the user decision is a 'Reject'.
The termination needs to happen immediately after the rejection happens without any deadline monitoring.
Can anyone please let me know how to set the work item to obsolete when the user decision is a reject?
Many thanks,
Raghav.

My bad....I was a bit hasty in answering that!!
Did you try activating the 'Processing obsolete' in the outcomes tab of the decision step? You should do that, and leave the path empty if you don't have any logic to add.
Let me know if this works.
-Krisnan
Edited by: Krisnan Kumar on Jul 29, 2008 9:24 PM

Obsolete and batch users can receive work items

Dear Experts,
Currently, we have found a problem that obsolete and batch users can receive work items by manual forwarding from someone. The roles and responsibilities of obsolete users were removed and users have been locked. For Batchuser, it's only created for some certain job with limited roles.
Could you help advise if this's a behavior of workflow or it's from some authorization problem? We have concern for business impact since no one is really handling work items and important messages are out of sight.
Thank you very much in advance.
Regards, Kae

Hello,
This is standard behaviour. It is even possible to send work items to users who do not yet exist (e.g. someone who is due to join the company).
The easiest way to workaround is to set up a substitution for any users that get locked and for background users. Personal substitutes can be maintained directly in table HRUS_D2, you could possibly write your own maintenance transaction for this if it is to be an ongoing issue.
Hope that helps,
Mike
Message was edited by:
Mike Pokraka

One of the user is unable to remove obsolete Tags from new work items and search query

Hi I am new to TFS Administration, User has some obsolete Tags in TFS site which is removed on the Backlogs but user can see those tags when he is creating new work items and while querying the Work Items but he is not able to see any obsolete tags in Backlogs.
TFS version: TFS 2013 SP2
Steps followed:
we queried each tags, we see 0 work items associated with the tags
As per MSDN, we have to remove associated tags which automatically removes the Tags after 3 days
The user is facing the same from past week
Am i missing something? or will the list of Tags be available in new work items and querying WITs? Please help
Thanks in Advance

Hi BE,
I tested this scenario in my TFS 2013 Update 4 Server, and found that Tags will disappear from Tags dropdown list automatically after serverl days, if there’s no any work item associated that Tags.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Need to set "Title", "Display Name" and "Name" fields to custom string property "RMA Number" for each instance of custom work item

Hi,
We have a custom Work Item we use to track RMA's. I've created a string property called RMA Number which is also used as a key.
RMAs do not have titles or any other identifying properties other than the unique RMA number (think incident number).
I was wondering what the best approach would be to set these other fields ("Title", "Display Name" and "Name") to the RMA Number value (RMAXXX), as I'm currently investigating using a powershell script via a workflow.
Thanks,
Pietro

Hi Marcel,
I've come up with the following:
# Load the SMlets module
Import-Module SMlets
# Get the RMA Class
$RMAClass = Get-SCSMObject -Class (Get-SCSMClass -Name MyWorkItem$)
foreach ($RMA in $RMAClass)
$RMANumber = $RMA.RMANumber
$RMA | Set-SCSMObject -PropertyHashtable @{"DisplayName" = $RMANumber; “Title” = $RMANumber; ”Description” = $RMANumber; }
Is it possible to make it aware of which RMA work item executed it, and only update that one? Updating all the records each time a new one is created will cause some problems in the future.
Thanks,
Pietro

Obsolete work item

Hi all,
I am thinking about this situation, when a employee create an Purchase order, it trigger my workflow to send a work item to his manager to approve the PO. If the manager doesn't go in his workplace and not see the workitem, but call transaction 'ME29N' to approve the PO directly. What shall I do with the work item stay in his workplace? Is this a problem or just let it go?

Hi,
The best approach would be to complete the workitem which can be done by terminating events.
Just get the event which gets triggered from ME29N for the approval of the PO.
Now, mention that event in the terminating event of the workflow, so whenever that event gets triggered the workflow will get terminated and the workitem will be removed from his inbox.
Regards,

Can I just add a state to bug work item and not set the state to the workflow

Hi,
Based on my team, we need to add a state/states to the bug work item, just add the bug state, and let it displayed in the state dropdown list. We don't want to add the state to the workflow. Can I do that?
Thanks,
shmily

Hi shmily,
If you add a state for the bug in your work item definition file, you have to define the transition for the state. If not, when you change the state, the backlog page or task board will not display the work item correctly.
Please check the links below for more information about workflow design guidelines and customization for work item type:
http://msdn.microsoft.com/en-us/library/ms194981.aspx
http://msdn.microsoft.com/en-us/library/hh409273.aspx
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to set status for work items

Hello Friend's,
As per my client current scenario every work item will be sent to 3 useru2019s .If any one of the user click on work item it will automatically call a Ztransaction for further action. Here if the user has viewed the item and back to sap inbox by clicking the back push button(in Ztransaction) without any modification or taking the any action(SAVE) then the rest of other user (2 users ) work items are disappearing from other user SAP inbox.
But my client required that whenever the user click on back button it should be READY status to all the users and it should not disappear from other user SAP inbox.
Please provide me any advice to the above requirement.

Hello Ranga,
that requirement is solved here: Automatic put back workitem after execution
But as it's quite an old one, it's hard to find here by the Forum's search option.
A more advance way could also make use of the work item exits.
Best wishes,
Florin

Delete credit memo work item created in VA01 when the user change value

Hi,
In T.code VA01 Credit memo request is creating, this document will automatically create work item. Based on Net value in credit memo request, the work item should go for 5 levels of approval. After 1st person is approved, the workflow initiator realized that the net value in created Credit Memo request is wrong; he is going to VA02 and correcting the net value. Again we have to create new work item for this and delete the already created work item. Client has clearly mentioned when ever there is change in 5 critical fields in VA02 then only create fresh work item otherwise no need to create SECOND TIME work item. Net value is one of the critical field in the list.
How to track already created credit memo request and how to delete the previously created work item. What is the feasibility of this requirement and how to handle this situation?
Regards
Vijay

Hi,
Just put a Fork and put 1 out of 2 outcomes and in the first alternative, you put your witem that goes to user B. In the 2nd alternative, put a Wait for event "CHANGED". And after this, put a process control step with "Set workitems to Obsolete" or "Cancel workflow" etc., depending on your requirement.
Pl note that this will only take out old witems, but you need to send a new witem for which you need to trigger another instance of the workflow as well. pl put CHANGED event also as one of the triggering events and use condition editor to restrict the fields that triggers the workflow.
Also, look into the IMG config of the following path. This might be a fitting solution.
In SPRO, go to Financial Accounting (New)---> Financial Accounting Global settings(New) -
>Tools --->Workflow ---> Workflow for Document Parking -->Reset Release Approvals(Customers).
Here, you can list down the fields, the workflow should restart. But, then you need to give the workflow details etc., in the relevant config settings.
We have used this in restarting workflows for General Ledger(GL) documents' workflow when some important fields are changed.
For this config settings, look into the following help link.
http://help.sap.com/erp2005_ehp_02/helpdata/en/01/a9cdd8455711d182b40000e829fbfe/frameset.htm
Hope this helps.
venu

Work Item to be disappeared from user1 inbox when escalated to user2

Hi,
I created a customising workflow for Credit Memo Request with 2 escalations for approval. I have used Fork operation to get this functionality with Requested start option in 2nd and 3rd branch to escalate after 3 and 6 days respectively if not the document is approved by the agent in branch 1.
Every thing works fine, but the client wants the work item to be removed from USER1's inbox when escalates to USER2 and from USER1 & USER2's inbox when escalated to USER3.
Could you guide how can we do it in my case.
Thanks in advance.
Edited by: Jaya on Sep 30, 2010 10:26 AM

HI Jaya,
you can make use of 'Processing Obsolete' here as it would remove workitems from the approvers inbox whose deadline is missed.
First of all , in the decision step make 'processing obsolete' active under 'outcome tab' of the task.
Use latest end with time as 3 days and action as modeled.Now in modeled deadline, make use of process control step and select 'set workitem as obsolete' and put step number of your dialogue step in 'workflow step'.
This will make the workitem diasppear from the approver inbox once the deadline is missed after 3 days.
Now to repeat the process fro 2nd and 3rd approver , put all of this in a loop, and before loop ends, find the next approver id in the outcome 'Processing obsolete' of the desicion step.and pass this id to the expression used for approver.
The loop condition can be a flag that is set to X when a deadline is reached. To do so, add a container operation in modeled deadline before process control step that will put the flag X.
So loop will continue to second pass if deadline is missed and hence so on till 3rd approver.Formulate condition for highest level of approval too.
Hope this helps.
Regards,
Sangvir Singh

Report to get cumulative effort based on child items related to parent work item

We have created a new work item type called 'Release'
Release -> Features -> PBI/Bugs -> Tasks/Test Case
I have requirement to create many reports that has to filtered across the Release work item been created. We usually slice it by Area/Iteration but here the requirement is different.
For ex:
Releases Overview report:
Release name| Owner as AssignedTo| Status Indicator | Completed Work | Remaining Work | Open Impediments
I can fetch all the release work items (Work Items with System_workItemType =Release) w.r.to team project for this report. But for other calculations :
Compute Open Impediments
Find all the child items belong to the parent 'Release work item'
Pick Open Impediments (Work_Item_Count with System_workItemType=Impediment and State = Open) in that list.
Is this possible by querying olap ? Or we need to go for stored procedures for querying warehouse?
please give a fair idea to start with and good resources for learning MDX.
Thanks
Divya

Hi Divya,
Thanks for your post.
To get the Release work items and all linked Impediments, you can try to create the Work item and direct links query, under Filters for lined work items section, set Type of trees = Parent/Child, work item type = Impediments and State = Open. Please refer
to the information in this document:https://msdn.microsoft.com/en-us/library/dd286705.aspx?f=255&MSPPError=-2147217396.
For such a Release Overview report, you need create your custom report. For the MDX resource, please refer to this document:https://technet.microsoft.com/en-us/library/ms144785.aspx?f=255&MSPPError=-2147217396.
Or contact SQL Server Reporting Service experts for the better response
And you can also create the work item report using TFS API.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to delete work items

Hi,
I'm using XI 3.0 and am trying to delete some Work Items that are sitting in Error status.
I've tried following OSS note 807906 but cannot see the menu items mentioned (specifically the Edit=>Change option) - can someone explain more clearly how to delete them?
Thx
Here is summary of OSS Note:
"First make sure that the process is actually 'irretrieveably lost', that is, that it has not simply encountered a temporary error (for example, the failure of synchronous sending and so on).
If you are certain that the process is no longer required, call the log of the affected process (using the process selection (SWF_XI_SWI1)) or the SXMB_MONI, ... and display the work item of the process (Workflows).
Go to the technical work-item display (if this is not displayed by default) and then select Edit => Change there.
Under 'Services for Administration', select the 'Logical Deletion' function.
This function is used to set the process to the 'Logically Deleted' status and to delete all outstanding correlations. The process has then reached its final status and can also be archived"

brian
are u luking into deleting error messages. If yes then,
SXMB_ADM --> Schedule/Delete Jobs
Delete Messages SXMB_MONI

HCM Forms&Process :Authorization error while opening work item in the UWL

Hi,
The process has been started successfully and the work item was appeared in the UWL of MSS.
But when I try to open the work item , I got the following errors:
"User XXXX doesnot have authorization on pernr 8000123"
"You are not authorized to process this process"
When I checked, the User XXXX has the required roles for authorization such as SAP_ASR_MANAGER and SAP_ASR_EMPLOYEE and the authorization object P_ASRCONT has been assigned to it as well.
Still why these errors are coming?
Does anybody know about it?
Thanks & regards,
Lek

Hi,
I have had exactly the same error. Make sure you have read the help.sap.com documentation carefully:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/43/3d8f8118391bcbe10000000a1553f7/frameset.htm. The minimum requirement is access to one infotype (it does not matter whether there is data in the infotype and it does not matter which infotype you choose) via CHECK_MIN_PERNR_AUTHORIZATION of BAdI HRPAD00AUTH_CHECK. More specifically, we solved it be providing access to infotype 0002 to all employees.
Furthermore, check what level of authorizations you have set in the config for the activities.
IMG->Personnel Management->HR Administrative Services->Authorizations->Define Authorization Method for Activities (All Processes) or Define Authorization Methods for Activities (for Each Process Group).
This should help you solve your problem.

Setting work item as obsolete

Similar Messages

Maybe you are looking for