Forum Replies Created
There is an example in the help files which, I think, will do what you are asking.
In your example you could use a formula to create your result; something like (Year * 100) + Month. This will give the calculation 201100 + 8 = 201108.
However this is only possible because you know the format and length of the data being input.
If you want to ‘join’ numbers where you don’t know the format then you could check one of the example forms in the help documentation. This is one of several useful examples that are worth checking out when you get a chance.
You can try the example out and will also be able to download a copy of the form to see the behavior used.
You can try using the ‘Show’ behavior command.January 14, 2011 at 4:39 pm in reply to: Finding the URL of a form instance without using a notify action #5566
The form instance has to be submitted before the instance URL can be produced. You might need to use the ‘Submit and re-open same instance’ option.January 14, 2011 at 9:31 am in reply to: Finding the URL of a form instance without using a notify action #5563
Use the Set Field behavior command and in the value section choose ‘Form – URL’ from the list of ‘Special’ values. You can do this to record the form instance link into your hidden field.
I can get it on the list for the reason you suggested and also another reason where it might be required.
If access to a form is provided via a link in a report then it is also possible for an unspecified user to open an instance. In such scenarios it may be useful to be able to manage the unspecified user.
I can see now how the option to have the ‘unspecified’ role available in the list alongside the ‘All’ roles would help in this particular instance.
I also appreciate that you found a way around it for your process but for the benefit of others who may be faced with the same, or a similar, issue they might consider creating a stage (perhaps called ‘returned for changes’ or ‘returned to submitter’) that the request is sent to if the stage 2 user decides that it has to go back to the submitter, (rather than sending it back to the default stage). The access rules can then be applied to this new stage so that only the submitter can make the changes.
Hope it helps.
If you have a support ticket already started for this case then it is better to use that method to resolve the problem, especially if it looks to be version related rather than a ‘how do I do this’ type of question.
I do have a comment on the ‘Default’ stage issue though.(This is mainly for folks who want to understand this topic a little better rather than for any possible release related issues mentioned previously).
At the default stage (i.e. when the form instance is first opened/created) there are no roles defined (Roles are only defined when a notification is sent to someone, allocating them a role, and this only happens when the form has been submitted) so there is no point in trying to set any access rules for specific roles at the default stage.
Furthermore only one person can access a form instance at the default stage; it is the person who will create the instance (who would normally be considered as the submitter/requester/applicant etc.) so the ‘All Roles / Default Stage’ combination would only apply to this person who is creating and submitting the form instance.
The exception to this would be if your logic is such that you notify other users (thus allocating them roles) in a way that the form instance does not move to the next stage … this is the only way (that I can think of) that a person with a specified role can access a form at the default stage. Although technically possible it is an unlikely scenario in most processes, and does not apply the very first time the form instance is opened/created.
There are several ways to manage field states, there are no hard and fast rules.
A common method is to use the All Stages/All Roles combination to set a ‘standard’ rule which would often be the rule that restricts access to the field (Read-only, Hidden or Disabled) and then use specific Stage/Role combinations to manage the exceptions to the standard rule.
Use the ‘Default Stage/All Roles’ combination to control the state of objects for a user starting a form.
There is a hierarchy that applies to the stage role combinations so that specific stage and role combinations will override the ‘All stages/All roles’ combination.
This is due to a recent upgrade in Flash. It has been reported to the development team.
The answer given by tmrhymer is quite correct and is a perfectly good method to use.
However, in order that you are also aware of other options, you can set the state of the form instance to Read Only by using the option in Form Properties | Advanced | Viewing.
This will also prohibit any changes to the form.
This should also be used in conjunction with the stage and role combinations described above.
Yes this is expected behaviour. It is so that you can report on data collected in previous versions of a form.
See here for more details
If you use a Connect command rather than a Connect & Search command, the lookup will run in the background and can populate form(2).
To enable the API reference behind the link button please make sure that API option is selected in the account settings. It needs to be enabled in the Settings section and also in your user settings.
The example form is now available to download from here.