Workflow Soluiton

I'm working on a project in which i need the "edit ticket" component to pull an incident number from a web form (the "incident number" process variable) within the workflow project. The problem is that when I edit the "edit ticket" component,  none of my process variables available. Any ideas? -Thanks

1) Make sure your EditTicketComponent has lines connecting it to prior components in your project.  Only components that are "connected" will show variables from upstream in the process.

2) Make sure your data types are matching.  For example, the EditTicketComponent wants to see an integer data type.  If you used a regular TextBox component on your web form to capture the incident number, then that result gets stored in a string (text) data type, not in a number (integer) data type.  To capture an integer, don't use a TextBox, use a NumericTextBox, and make sure to change it to Integer instead of decimal (since a ticket number will not have decimal places).

Thanks a ton Chris. A numeric text box did the trick. Still kinda new to workflow so this has been a great learning experience.

That's a very common error. Once you use the tool a little bit longer, you'll get used to how datatype-centric it is. This is a good thing, because it forces you to use the right variables in the right places, but it does take getting used to at first. Good luck!

Any pointers on how to format the numeric text box to not use a comma in a number with more than 4 digits. Our tickets currently are at five digits, so when a user enters a ticket number in the numeric text box it shows up as 47,489 rather than 47489. I've tried every data mode available but none yield the desired format.The workflow still works as desired but I would like to have the form show the ticket without that comma since that is how incidents are displayed everywhere else.

I have not found a way to have it display a comma in the NumericTextBox or NumericStepper component.  As you probably saw, though, it is just a display thing...the number still gets stored in the variable without the comma (of course), and if you later display the number, e.g. with an ASCII Merge Label or in an email, it does not print the number there either.  So it's just a little annoyance for certain number types.  

If it was worth it to you, you could use a textbox control to input the ticket number first, and then later use a Get Number From String component to convert that ticket number (text) to ticket number (number).  You could put custom validation on the form itself if you were concerned about letting them exit the page having typed in a non-number.  Neither of these would be very hard to do, and would give you a no-comma field to enter the number into.

Worked like charm. I used the "Get number from string component" to convert it from text to numeric, had "value is not a number" flow into another form that tells the user that the number is invalid and prompts them to revise the incident number. They press OK on the second form which flows back to the original so the user can make necessary changes. Thanks again.

...you might find it more convenient to use custom validation on a form.  I've described how to do this with validating an email address in your other post, here:

https://www-secure.symantec.com/connect/forums/validating-email-address

The advantage is you never leave the form so it makes designing your form flow easier.  Good luck.