Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 2 down vote favorite
1

Process:

  1. User Creates Item
  2. Admin receives "approve this" e-mail with a dynamic link
  3. Admin selects dynamic link in e-mail
  4. Admin is taken to initiation form of second approval workflow
  5. Admin selects approval check box, hits OK, workflow updates status and enters log info
  6. Everyone is happy

This was easy in MOSS - just create a dynamic hyperlink: {Site URL}/Workflows/{Workflow Name}/{Workflow Initiation Form Page}?List={List ID}&ID={Item ID}

In SP2010, it seems to demand a different style: {Site URL}/_layouts/IniWrkflIP.aspx?List={List ID}&ID={Item ID}&TemplateID={Template ID}

The Template ID changes whenever the workflow is edited - which makes this whole dynamic process just a little less dynamic. I can't find a variable that matches Template ID anywhere in the new Workflow Context menu - and so no way around having a more formal change management process when it comes to these particular workflows.

Does anyone know of a way to get a dynamic variable for that Template ID?

share|improve this question
This is also driving me nuts.. do you have already found a solution to this topic? Thanks and kind regards Fabian Edit: I got a solution which works for myself.. Maybe it will help you to get your solution work: Instead of using an (unexisting?) dynamic variable for template id value, I took the feature ID which is listed in the workflow feature properties. This ID seems not to change and fits my requirements. – Fabian Jun 5 '12 at 6:26
why don't you start a workflow at item creation, then create a task for the admin, with an email notification ? – Steve B Jun 5 '12 at 7:13
@Fabian - Does that end up looking like this? {Site URL}/_layouts/IniWrkflIP.aspx?List={List ID}&ID={Item ID}&FeatureID={Feature ID} – Cory M Jun 6 '12 at 20:31
I have a suspicion that Microsoft made this change as a way of "resolving" a separate issue where designer doesn't always "take" your latest change to a workflow because it's reading from localcache. This no-longer-dyamic URL plus the new requirement to Publish a workflow, I assume, makes it much more reliable that SharePoint is going to run the latest and greatest. – Cory M Oct 12 '12 at 14:09

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.