Skip to main content

With the client event wizard, there is an option "append serial number to url" which is great for someone working with default url scheme.

In my application, I'm using some routing scheme and want to put the serialnumber in the middle of my url:

http://application/url/{serialnumber}/actionname/form.ext

the problem is that would make the url look like that  http://application/url/SN=123_456/actionname/form.ext which i'm unsure if it will work

the problem is that I'm unable to pull action and process id from the "workflow context browser" pane, the drag-n-drop doesn't work as expected

I would like to have something like this: http://application/url/{processInstanceId}_{activityInstanceId}/actionname/form.ext

Is there anyway to parametize the url the way I need?

You can't use the Process Instance ID and the Activity Instance ID in the Web Page URL field.  However, you can still use the default serial no field which should be the same thing.  i.e.  http://application/url/<SN={SERIALNO}>/form.ext


If I recalled correctly, you can't use the actionname property as it will not be populated at the point of workitem generation.

Thanks for your answer,

if any workarround is available to get the process id and action id part separated and usable as part of the url, it would be great (the SN=*** in the middle of the url doesn't feel right)

Is there any place in the documentation of what fields will be available or not at various place in the wizards?

by the way I didn't mean to use action name, it was just a random static value in my sample url

  

I am not sure why it was disabled,but there could be a reason behind it.  If you have a customer or partner account, the best bet would be to submit it as product feedback with the reasons for the request.  This will allow the labs team to analyze it and see if it is a valid feature request.

Thanks for your feedback Johnny,

I'll post the feature request as soon as my partner account is up.

In the meantime, someone (thanks Jean!) gave me a work-around which is to type {SERIALNO} manually in the url which is latter substituted by the client event code

 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings