I have an infopath form which users use to fill details and approver approves. The approver section in form is displayed to only those whose ID is present in hidden field. This was working fine before but now even approvers could not see approver section. Recently I added an user in hidden field after which it worked fine for sometime. Now all approvers could not see the approver section itself.
Things to check:
if you are using multiple views in the form, make sure you are updating them as needed and not only updating one view and forgetting the others.
if you remove the lase user you added tonthe hidden input, does the issue go away? How are you inserting users in hidden input? Seperating them by some character?
try to display the id of the current user in the form and display the hidden input and make sure the id's really match or there is any difference
Related
There is a setting for forcing story points to be entered when creating a work item (e.g. user story) in the layout processes field options, but is there one for mandating linking of work item/story to a parent?
There isn't a straight forward way to do that.
A good option is to create a custom field in User Story work item in your inherited process.
And set the work item rule to make required the value of this field when creating User Stroy.
Check the UI output by using the rule. This could be a reminder to link the parent work item.
Update 1:
You still need to manually add link as Related Work.
The required value for the custom field works as a reminder for the users when creating the User Story.
You could also define the custom field as Picklist(string). When a user creates a new User Story, he could add Related Work links and pick a value for the custom field in order to save this User Story.
Output:
I'm currently working on a user registration form for a site I'm working on. The site requires a lot of information about users up front, and I'd like to break it down into stages.
The first stage requires the user to put in an identifier in the form of an order number. I would then check the order number exists in the system before making them continue to fill in the rest of the fields. I'm not sure how to go about doing this.
What I've managed so far though is to override the underlying User, RegistrationController and RegistrationFormType and render out a customised view with the relevant form fields.
An overview of the process I'd like would be:
FORM: ask for order number
process form and check order number exists (if not go back to 1)
FORM: ask for user information
process user information and store
complete
Simplest way of doing it will be to override registration template, and hide all fields except those you wanna show in first.
And than add some js validation rules, - to show up parts of form based on values prefilled by user. In that case you do not need to rework Sonata registration form, but for user experience it will be the same.
I have a long form that an user has to fill. After the user has clicked submit, I have to show a page with the information the user has filled in the form so that he can check that everything is correct before doing any further processing (i.e., he has to press another submit button or a back button if he detects an error).
Is there an easy way to do this? Is there a better way than creating a new form with hidden values equal to the values submitted in the previous form?
Would it be okay if I just store the information in a session variable and then process it if the user confirms?
You could skin that cat many ways, here's a couple of ideas:
Add a non-mapped confirm input (like a checkbox) to your form. On initial form render with no POST, hide the input. When you get a POST, show the checkbox input & some additional information (please review your data & check to confirm all is OK etc). Don't validate the form or save your data until the confirm input has been checked. You don't need to mess about with hidden fields, the one form will do the job for you.
Save the entity and give it a property e.g. isApproved, that way you can show the data easily & if the user needs to edit, re-use your form. When the user approves the information set isApproved to true. Don't perform any actions on any entities that have isApproved == false. Cons are you then have to manage an isApproved state for an entity.
in the field usage section of tuleap, i have selected bind to users option, in that i selected list of groups available and also artifact_submitter option.
So,when a submitter(user1) fills the task and assign it to the user2, the assigned person couldn't assign back exactly to the particular person(user1), who submitted the artifact.When user2 selects a assigned to option he can see the artifact_submitter along with the usergroups involved in the section.
In our office we have some 150 users who will submit a artifact and assign it to the project lead user, in turn the project lead couldn't assign back to the exact user who submitted it.
When he clicks the assigned to option, he could able to see all the 150 users available for that user group.
Is there a option where one can assign back to the exact user whoever submitted the artifact.(like we have correspondence button in Codesk tool)?
Sadly no, this is not possible at the moment. What you can do is use an Openlist field instead, which does not solve your issue but make it easier to select one person in a list of 150 name.
Newbie to sharepoint but this thing didnt work for me as expected.
I am trying to have a sharepoint form:
1)Where accounts fills in section (presses submit, email sent to IT to fill in their section)
2) IT gets email, go fill in their section(press submit, email to MD to approve /reject)
3) MD approves/rejects
4) data saves
I have the form working, and using views am able to go between forms.
Issue is how
1)email alert to groups
2)half filled forms, given to other groups
Thanks
To Solve your first problem :
You can create an event reciver which will fire when an item is created in the list as well as when an existing item is changed in the list Or you can also create a workflow for this too.
There is an approval workflow OOTB which may be helpful for you too, but i am not sure about that.
For the Second question :
Whenever you open the existing item again, infopath form will automatically manage the data entered in the form and displays it as filled data.
Hope this helps.