Reject workflow

I may be crazy, but I think the "Reject" UI behavior used to be different.
When I have the Browser on one screen, and a full screen preview on the other, I'd like to quickly reject photos and have Aperture move to the next photo. I have a pretty high reject ratio, and currently I have to reject, hit right arrow, hit reject, etc.
I swear Aperture used to behave differently. Maybe it was back in 1 or 1.5, but I seem to remember being able to repeatedly hit reject to quickly cull my photos.
Does anybody know of a way to make it behave like that? thanks

The Command Editor is a bit Yoda-like -- very powerful, laconic, and inscrutable.
With the Command Editor open, click the on-screen representation of the 9-key.
In the "Key Detail" pane, click the oval-ended gizmo "Reject" and drag it from the "No Modifier" spot to the "Command" spot. In like manner, move the "Reject and Move to Next Image" gizmo to the just vacated "No Modifier" spot. Then move the "Reject" gizmo to the "Control" spot. Click "Save" and then close the Command Editor. Try your newly re-assigned keyboard shortcuts.
If you hadn't already created a custom Command Set you will be prompted to do so (you can't alter the default set).
The User Manual contains a [thorough section describing the interface|http://documentation.apple.com/en/aperture/usermanual/index.html#chap ter=27%26section=4%26tasks=true], but not much on how to actually use it. You may find it helpful. Their instructions are different than those I've given you above.
"Gizmo" is not official Aperclature.

Similar Messages

Reject workflow notification which is in notified stage

hi all,
how to reject workflow from notified stage to reject stage from back end using any api or any procedure.
please help me to find the problem..
best regards,
Ram

How is this issue related to an Oracle product download?

PO Release / Reject WorkFlow

Hi
I have a scenario for PO Release / Reject Strategy . It is a Three Level Approval Process . If a PO is saved , the Work Item has to goto first Approver for Release and after he approves it has to goto Next so on . If the Approver reject it has to go back to the Previous approver and if he rejects it has to goto the Previous guy and so on .How can it be done in one WorkFlow Process.
Thanks

Hi BK,
you need to create a process logic here.
I doubt if std.WF template has this logic.
In PO tables, there is a field which ammends 'X' in every release done.
Say there are 3 levels of approver, if approver 1 approved, the field would be 'X' if 2 approves it would be 'XX' and so on till eight levels (if Release Strategy is maintained)
So somewhere in your logic you need a container which fills this and using this container you need to track the approver and send the rejection notification.
So hint, combination of LoopUntil Step, CheckCondition Step and may be Process Control Step at the end.
Hope it helps.
Aditya
Edited by: Aditya Varrier on May 16, 2011 2:06 PM

CATS Rejected workflow

Hi friends,
we are in ecc 6.
Can someone tell me the purpose of Rejected event in BO CATS? Whenever a timesheet approved or rejected, COMPLETED event triggers. Never Rejected event is triggering. I want to send an email to creator of timesheet in case his timesheet is getting rejected. Standard task 31000007 sends notification only to sap inbox. note that it is just a notification, no workitem is generated. so i cannot use RSWUWFML2.
Thanks
NAsh

Hi John
Can you act on your previous threads, please?
You have got quite a few that haven't seen any input from you. There was a recent one from you about a termination workflow and though there were responses, you didn't bother to show the basic courtesy to reciprocate.
Make sure you have either sufficiently responded if you cannot clsoe the thread.
Regards
Ravi

First rejection workflow

Here is my workflow, and it is just running though the approvers serially. The problem is, is there isn't an option to fail on first rejection like there was in SPD 2010. What do I need to do?
Stage:Stage 1
Set Workflow Status to Pending
Start a task process with X; Y; Z; ... (Task outcome to Variable: Outcome )
If Variable: Outcome equals Approved
Set Workflow Status to Approved
Update item in Current Item
If Variable: Outcome equals Rejected
Set Workflow Status to Rejected
Update item in Current Item
Transition to stage
Go to End of Workflow

Hi,
We can use the
SPWorkflowManager.CancelWorkflow method to achieve it.
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/2c0e0211-4ca9-48f6-876b-73d1505411bb/cancelonrejection-workflow-sharepoint-2013?forum=sharepointdevelopment
More reference:
http://blogs.msdn.com/b/officeapps/archive/2013/03/27/sharepoint-workflow-development-with-office-developer-tools-for-visual-studio-2012.aspx
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

UWL Approve/Reject - Workflow Container Element

Hello,
I have a custom WF which uses a task copied from a standard. It is a User Decision task based on TS20000135 (Check Trip Facts).
If the user rejects the trip he will need to Add a Memo which will be bound to container element AttachObjects.
To test the existence of an attachment, I have a completion based on this field but I also need to check if the user pressed the "Send trip back for correction" or "Reject" button, otherwise he will also have to enter a memo in case he approves the trip.
Anyone knows what is the WF Container Element that will contain the action value?
Moreover, does anyone know what are the values for each action? (i.e. Approve, Reject, Send Back).
Thanks in advance
Antonio

This value will appear in the task container of a decision task. I think it is of type SWD_LINES-RETURNCODE. I feel the container element is RESULT. This element gets created default in a decision task. Check the standard Decsion task 8267. Generally it returns a 4 digit number. Suppose you have 3 decision it will return 0001,0002 and 0003. Just analyze that Container Element in the task and you will resolve Ur issue. Test and find out which number returned is corresponding to your decision.
Thanks
Arghadip
Message was edited by:
Arghadip Kar

Is it possible to create forms and workflow by Workbench and manage them by ContentSpace?

Hi,
In a previous issue, I have asked the interrelationship between Workspace and Contentspace. I learned a lot, and I'm very appreciate the kindly answer from Hodmi and Jasmin. And this time, I want to ask something about Workbench and Contentspace.
As a part of presentation for a corporate client, I am trying to make a demonstration model. I 've created a PDF form and an Approval-and-Rejection workflow by Workbench. And I want to upload the form and the workflow to the Contentspace.
In my imagination, I would make a button in the form, and then when I click the button, the form will be sent from the client side to the server side. As a result, it will appear on the space which I specified in Contentspace.
About the workflow, I guess the Contentspace and Workbench may have some common place about Process Management and there is some transportation mechanism or something else between them. So by changing some configuration the workflow could be added into Contentspace.
It is totally selfish imagination, but if it is possible, I think my corporate client will be more interesting about Adobe Livecycle.
Beg your help.
En Shoku

Let's me just try to answer to question in several pieces.
"And I want to upload the form and the workflow to the Contentspace."
You can definitily save the form in content space. I'm not sure what you mean about the workflow.
"In my imagination, I would make a button in the form, and then when I click the button, the form will be sent from the client side to the server side. As a result, it will appear on the space which I specified in Contentspace."
This is also possible.
"About the workflow, I guess the Contentspace and Workbench may have some common place about Process Management and there is some transportation mechanism or something else between them."
You need to use the ContentSpace service. The Content Space service gives you a bunch operation like storeContent, retrieveContent, etc. You can use that service in Workbench, or call it directly using SOAP or REST.
So to summarize, you can use the Content Space service to interact with content space to get and store your forms for you workflow.
Jasmin

Workflow function modules

I have a problem in my workflow email
creator submitted a request to approver through workflow.
work flow needs to send an email to approver that part is working fine for me.if request approved or rejected workflow needs to send an email to creator that part is not working for me.
is there any function module or class to send email to creator if something is there please let me know.
Thanks,
Message was edited by: priya katragadda

Hi Priya,
You can create a worflow container element which will have ID of request creator.
Pass this element with value of request creator as input to your task which will send mail. Your task have to used requestor ID to determine whom to send the mail.
Since you have already done half part ie. to send mail to Approver it will not be uch difficult ot send mail to Request Creator.
Regards,
Pl. reward useful replies.

Oracle UCM custom Criteria Workflow

I am looking for some help.
I am trying to create a criteria workflow based on a document type. I have used the command wfrelease to commit all metadata to the repository in the entry step.
The user in the workflow will either approve the workflow or select from a custom metadata field option list called "status". Once a user sets the value to "rescan" in the "status" option list I want the user to reject the workflow. Once rejected we want the workflow to be sent to an alias and not the original author.
If the user sets the value of the "status" option list to either "return", "reroute", or "invalid" value and rejects the workflow then I want the workflow to be routed to a different alias.
Is this very difficult to accomplish? What steps would I need to create? I am pretty sure somehow I need to create tokens for the 2 different aliases and call them on reject but I am having trouble putting all of this together.
Thanks in advance for your help!

Hey Data Bitz
The good news is that yes, all this can be done with some configuration and a bit of workflow scripting.
Several items:
1) I'm not seeing a reason why you need to use WfRelease in the entry step. Workflow users can still access and alter the metadata for routing as you describe. Do you want the item to be indexed (to appear in the search results lists)?
2) While there are several ways to do this I would envision a two step workflow. Step one is your "rejection handler" step 2 is your user review step.
first time through content passes through step one with a criteria based jump in the entry event of that step. The criteria is along the lines of if step entry count <= 1 then jump .
Make sure that step one is an edit and review step. Step two is where the user either approves or sets the status metadata field to some other value. If s/he approves, the content is released (or goes on to subsequent steps).
If the status is changed then you want to trigger a rejection. This brings me to point 3...
3) Do you want "rejection" or do you just want to rout the content to another set of users for review. The reason is that rejection is logged as a "rejection" Workflow Action in the database. If you are tracking or reporting against this then you'll want a "real" rejection. If you just want the item to be routed to an alias that is based on the value of the status field then this is different and can be achieved without a full blown rejection action. The choice is yours and the impact is really just on reporting and the routing behavior of the content object.
4) so lets say the user sets the status to "rescan". Remember we're in step 2 here. Use the update event of step 2 to look for the Metadata Update action. Because the update event of the workflow step acts like a loop it is able to pick up the metadata updates that the user executes. Configure a jump in the step event to say +if there has been a metadata update action then check the value of the status metadata field. if the value of the status metadata field is "rescan" then perform this action, if the value of the metadata field says some other value (either "not rescan" or "return", "reroute" etc) then perform this other action+
5) So if you really want a true rejection then the this action from above will be a bit of IDOC to execute with WFREJECT service. You'll need to pass along the appropriate parameters for the service (see pp 348/349 of the services reference guide for the WF_REJECT service and required parameters. The guide is here: http://download.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/documentation/developer/services_reference_10gr3en.pdf). If you just want to route the content to another set of users then the this action and this other action are actually the same and you can jump back to step 1 with a jump script. While the actions are the same, the users will be different and we can handle this with some basic workflow configuration scripting as well. Now here is where the fun begins.
6) So you're back in step 1 either because the WF_REJECT action happened or because you jumped here. The status field set to "rescan" or some other value like "return", "reroute" etc. Go back int the entry event of step 1. This is where the pass through code from item 2 above was written. The cool thing about the entry event is that it gets evaluated BEFORE step users are set and email notifications go out. This means that you can set any kind of user decision logic right in the event. So beneath the pass through code I would create another block of workflow scripting that does the following: gets the value of the status field - you can do this simply by referencing the metadata field name - e.g. myVar=xStatus. If myVar="rescan" then set a companion file variable to the name of the alias you want - e.g. +<$if myVar="rescan"$><$wfSet("reviewerAlias","YOUR_ALIAS_NAME")$><$endif$>+ If you're unfamiliar with the companion file, see pp 18 of the workflow implementation guide (link below). Think of it as a temporary memory cache for each item in workflow. It is a place where any key value pairs can be set and retrieved for any document as long as it is in workflow. Keep setting the value of "reviewerAlias" to the different alias names based on your IF condition. for example:
+<$if myVar="rescan"$><$wfSet("reviewerAlias","YOUR_ALIAS_NAME")$><$elseif myVar="return"$><$wfSet("reviewerAlias","YOUR_OTHERL_ALIAS_NAME")$><$endif$>+
7) Finally you have the content in the right step, you have evaluated the metadata and have set a variable in the companion file with the correct alias name you want to be the users for the step. The last thing is to retrieve that alias name and set that alias as the step user. Remember that workflow is able to set either individual user names (singly or CSV) or ALIAS names as step users. Remember that an alias in UCM is a list of user names. You will use a token in step 1 to retrieve the value of the companion file key and set the alias to be that user. The token code is straight forward but if you want a walk through then check out the adding ad hoc step users section in chapter 9 of the workflow implementation guide here:
http://download.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/documentation/admin/workflow_guide_10gr3en.pdf
Your token code will look something like this:
<$wfAddUser(wfGet("reviewerAlias"), "alias")$>
The wfAddUser function is the token code. It is what adds the step user and it take two parameters - parameter 1 is the name or names of a user or alias. parameter 2 is the type either "user" or "alias".
So this give you a fully dynamic workflow that allows the routing of the items to be fully dynamic and driven off of metadata - something that is very easy for end users. It also allows the reviewers to be dynamically set using tokens and a bit of idoc. No coding outside of the workflow admin applet has to happen at all.
Of course, my company, Fishbowl would love to talk with you more about what you're doing and see if we can provide any additional service to you. Please let me know!
Warmly,
Billy Cripe
Fishbowl Solutions

Reject PO

Hi friends,
I am using the separete standard workflow WS65400030 for PO reject . Now it sending mails to PO creator.
but I am working on release staratagy by using the RELEASESTEPCREATED event. when ever PO created this event is
traiggring .Then mails are going to Approvers ... but when I reject PO, these workitems should be disappeared. I mean release statagy workflow should be terminated
or
Is it possible both RELEASESTEPCREATD and REJECTION_STARTY in same work flow , if it is YES, Please give me the suggestions.
thanks for your time.
regards,
Aj

Hi Ajay,
There is no different approach for PO reject Workflow unless you are using same release code. You need to specify the PO Rejection as terminating event to complete the workitem pending for PO release. If you want to model the flow based on this event, then you can specify this in the triggering event of WF/WI.
Regards,
Vaishali.

3 different workflows are getting triggered. Please suggest

Hello Experts.
i saw a new issue with the PO release strategy that, for certain PO's When the po is successfully released automatically PO CHAGNE and PO REJECTED workflows are getting triggered.
This is happening with only few PO's Not all.
If it is related to Event raise of CHANGE nd REJECT , for every PO release they should trigger ryt.
But only for certain po's its happening. And user says they never changed or rejected the PO'S and they are successfully released.
I Verified to some extent but no use
Can you suggest.
Regards
Prasad CH.

Hello Modak.
This is want happend in event trace. PO was changed on 1/1 and Change event is raised on 18/8
I wanted to know what does this EVENT DATA & TRACEDATA in swel(after double clicking on the event in swel)
Issue is, for a workflow event trace, it says EVENT CREATED ON 1/1/2014 (in event data) and EVENT TRACE DATE/TIME 18/8/2014(trace data).
Here in 1/1/2014 there is an event created CHANGED.but the worklfow did not start then.
It was started on 18/8/2014. By that time the actual release of PO completed and this workflow again started saying PO changed.
If i verify event trace by date for 1/1/14 and 18/8/14 it shows the same
I verified both the CDHDR and CDPOS and see the entries are changed on 1/1/2014 only.
How can this happen???
What does this EVENT TRACE DATE/TIME mean??
The event even created on 1/1/2014 the workflow starts on 18/8/2014 as per the EVNTTRACE DATE.
Please Advice.
Cheers
Prasad CH.

Error while reading Swd_Header table in workflow.

Hii,
For Pr rejection workflow i have created one Zevent.Inside workflow for User decision derived one rule
which is ending in following error.
Database error '4' reading table 'SWD_HEADER'
The function module for rule 'AC99900003' initialized an exception and returned a message.
I am not able to understan from where n why it is trowing d error.Thne FM written for rule is properly retriving the value.
Pls help me to solve the issue.

Hi Nivdedita,
Check the rule which you have defined in the workflow.
Regards,
Sravanthi

Are there WF Signature Request "Rejected" notifications?

In GSM WF, we have a step that requires a couple of Signature Requests from different functional areas. We have noticed that when a signer rejects to "sign" that no email notification is going out to the owner of the step. This is counter-intuitive to user experience and different than the way Supplier notifications work on SRSA workflows. Is there a configuration to turn the GSM WFA Signature Request Rejected notification = "ON"? If there is no configuration option, how have others solved this? Are your users asking or have asked in the past for notification when another rejects their spec object?
Thanks! --Beckie

OK, let's go over how this gets implemented:
NOTE: Remember that this would be a custom solution. We are working on improvements to signature documents for an upcoming release.
Because Signature Documents have their own workflow, we can add a workflow action (class) that gets triggered when a Signature Document moves from Review to Rejected/Not Approved. The Signature Document workflow is not managed in the UI, so to add a workflow action, we will use a simple database script. The custom Workflow Action class can send an email to the specification owners informing them that a signature document was Rejected, and include some helpful information.
For example, the email body could look like the following:
A Signature Document was Rejected for the following specification:
Spec Number:     5112558-001
Spec Name:        Papaya Pineapple Juice
Current Status: Design
Signature Document Rejected by:
User:    John Doe
Reason: Missing custom section XYZ details
Click to view the signature document --> http://<servername>/gsm/BaseForms/frmSignatureDoc.aspx?SpecID=5816d6dc0945-a9b7-43d4-82f0-235b7b6946ff&SigDocID=5769d6654ad6-e77a-4264-bf71-0a45fac4338f
Steps:
1. Create a new Visual Studio project (or potentially use an existing one if you already have one for workflow actions or validations)
2. Add the following PLM for Process DLLs as References (get them from the SharedLibs folder of your release):
CoreAppPlatform
DataInteraces
DataLib
DataObjects
GeneralServices
GSMLib
LinearWorkflow
PluginExtensions
ProdikaCommon
ProdikaLib
WorkflowCore
3. Create a new class that extends the SimpleLinearWorkflowActionBase class (from Xeno.LinearWorkflow). Here is a reference example (note this is an example class and is for demonstration purposes only):
using System;
using System.Collections.Generic;
using System.Linq;
using Xeno.Data;
using Xeno.Data.GSM;
using Xeno.LinearWorkflow;
using Xeno.LinearWorkflow.WorkflowObjects;
using Xeno.Prodika.Application;
using Xeno.Prodika.Common;
using Xeno.Prodika.Config;
using Xeno.Prodika.GSMLib.Workflow;
using Xeno.Prodika.Services;
namespace SampleWorkflowExtension
    public class SignatureRequestRejectionNotificationAction : SimpleLinearWorkflowActionBase
        public override void Execute(ILinearTransitionContext ctx)
            var transitionContext = (SignatureDocLinearTransitionContext)ctx;
            ISpecificationService specService = GetSpecService();
            if (specService != null)
                var currentSpec = (IBaseSpec)specService.Current;
                var specOwnerUsers = GetSpecOwnerUsers(currentSpec);
                if (specOwnerUsers.Count > 0)
                    SendEmailToSpecOwners(specOwnerUsers, transitionContext.SignatureDocument, currentSpec, transitionContext.Comments);
        private static List<IUser> GetSpecOwnerUsers(IBaseSpec currentSpec)
            return (from ISpecOwner specOwner in currentSpec.SpecSummary.Owners.Values
                    select AppPlatformHelper.DataManager.objectFromID(specOwner.OwnerID)).OfType<IUser>().ToList();
        private void SendEmailToSpecOwners(List<IUser> specOwnerUsers, ISignatureDocument sigDoc, IBaseSpec currentSpec, string workflowComments)
            var userService = GetUserService();
            string currentSigDocUserName = userService.UserContext.User.Firstname + " " + userService.UserContext.User.Lastname;
            var specSummary = currentSpec.SpecSummary;
            var currentUser = userService.UserContext.User.ContainedUser as IUser;
            if (currentUser != null)
                string from = currentUser.email;
                string to = StringHelper.Join(specOwnerUsers, x => ((IUser) x).email, ", ");
                string subject = String.Format("Signature Document Rejected for Spec {0} ",
                                               currentSpec.SpecSummary.FreeTextName.Name);
                string body = String.Format(_emailBodyTemplate,
                                            specSummary.SpecNumIssueNum,
                                            specSummary.FreeTextName.Name,
                                            specSummary.WorkflowStatus.Status,
                                            currentSigDocUserName,
                                            workflowComments,
                                            DeploymentConfig.GetAppURL("GSM"),
                                            specSummary.SpecID,
                                            sigDoc.DocId);
                EmailService().SendMessage(from , to, subject, body);
        //todo: this should be in the database as a translation
        private const string _emailBodyTemplate = @"A Signature Document was Rejected for the following specification:
Spec Number:     {0}
Spec Name:       {1}
Current Status: {2}
Signature Document Rejected by:
User:    {3}
Reason: {4}
Click to view the signature document --> {5}/BaseForms/frmSignatureDoc.aspx?SpecID={6}&SigDocID={7}
        private static ISpecificationService GetSpecService()
            return AppPlatformHelper.ServiceManager.GetServiceByType<ISpecificationService>();
        private static IUserService GetUserService()
            return AppPlatformHelper.ServiceManager.GetServiceByType<IUserService>();
        private static IEmailService EmailService()
            return AppPlatformHelper.ServiceManager.GetServiceByType<IEmailService>();
4. Compile the class and place the dll into web\gsm\bin.
5. Run the following database script to add the workflow action to the Reject workflow transition, replacing the classname, namespace, and assembly (in green below) name to your classname and assembly name. SigDocRejectSample is just a reference name for this workflow action - you can change it to something more meaningful:
insert into gsmWorkflowActionTemplates
values ('57602CF17ABE-9AF7-4E32-9A61-76DF5AA0E09C', 'Class:SampleWorkflowExtension.SignatureRequestRejectionNotificationAction,SampleWorkflowExtension',
'57574dd649e7-2454-4d84-a0f3-7377d6d2c57f', 'SigDocRejectSample', 0, 0, 0);
6. Restart the GSM application
That's it! You should be ready to test it out.
Note that this sample has the email subject and body written in the class, and written in English. Ideally, to support multiple languages, this should be added to the database, into the commonXLAExtensionCache and commonXLAExtensionCacheItem table. I will write up a followup on that or handle it in an upcoming Dev To Dev.

Approving Workflow Emails on Blackberry

Hi All,
We want to implement approve/reject workflow notifications from blackberry devices.
Can anybody provide step by step implementation proecure OR suggest some documents ?
We are on Oracle eBusiness Suite 11.5.10.
Regards,
Mahesh
Edited by: ksmahesh on Jun 8, 2009 10:42 PM

Approving workflows via Black berry, Are the users going to view their emails on a black berry if that is the case then the new version of the OS on black berry enables you to perform the approvals.
Thanks,
Varun

DMS & Workflow - Handling Digital Signatures

Hello,
I have set up a DMS status network, and I'm controlling this network using workflow.
My workflow listens to "DRAW" for changes, and when a particular status is seen,
workflow starts.
This workflow sends out work items to several users, prompting them to review.
At this point, users can go into the DIR from their Inbox, and either select Approve or Reject Status.
Both Approve and Reject status are set up to require a Digital Signature. Workflow controls moving the status back to a "ready" state for the next reviewer. It also keeps track of the number of reviewers, in order to know when all reviews are done.
When everyone behaves in timely manner, this works great. Workflow has no issue with setting DMS statuses - in most cases.
However, I also have deadline monitoring set up on my workflow. After 3 days pass with no action, I want to "auto-reject". System id WF-BATCH is what I use to set statuses through workflow, and this works fine in most cases. However since the status "Approve" and "Reject" are set to require digital signatures, this system initiated status change FAILS. The system does not provide a digital signature for itself.
My question is - is this possible through configuration - to set it up in some way that a system ID can promote to a status and either pass a password or simply not require a digital signature?
My network is kind of stuck at this point because one of the 2 statuses MUST be selected for it to proceed.
Edited by: Bill Bessette on Jul 24, 2008 9:40 PM

Hello Niranjan,
That's an interesting suggestion... I'll investigate. Any additional detail you can provide on how to implement this User/Pwd hard coding in WF would be appreciated.
In the meantime, here is some additional info.
Imagine a status network as follows:
Draft
Initiate Workflow
In Review - Reject/Approve
Active
Document starts in draft. The author selects a status of (Initiate Workflow) at which point the workflow starts.
Workflow moves the status from (Initiate Workflow) to (In Review)
and puts a work item in the reviewers mailbox. Reviewers can change the status to (Reject) or (Approve) and each requires a digital signature. After each reject/approve, Workflow moves the status back to (In Review) so that the next person may act. When everyone has reviewed and approved, workflow moves the status to (Active). If anyone has rejected, workflow moves the status back to (Draft.)
This is a simplification, but that's the scenario. WF-BATCH is our workflow ID that has SAP-ALL authorization. Problem occurs when deadline monitoring is in effect. If a reviewer doesn't act within the designated deadline, the monitor fires and the work item is flagged as obsolete. Due to the status network, the only valid path is to either move to (Approve) or (Reject). But since both of those statuses have been set up to require digital signature, they fail. We end up stuck in (In Review) with no way out.
If hard coding the userid WF-BATCH and the password in some table will solve this problem, then we'd be thrilled.
Bill
Edited by: Bill Bessette on Jul 25, 2008 6:00 PM

Reject workflow

Similar Messages

Maybe you are looking for