when i check the application status history tab of New Business License application ,i got confused by the same statuses multiple times. When clicking the form only we came to know who returned/approved the form? Is there any way for the user to know from the history tab itself without clicking on the form
There is no other option as of formsflow.ai v4.0.4 to show what changes are modified in case of monitoring Application History.
It depends totally upon the workflow you design, how the applicationStatus changes across each stage of workflow. So if you are confused by multiple status happening at same time, you can redesign the workflow in such a way.
Related
When we are doing the customization of a work item type in VSTS. Do we also have the ability to track the history of the customization itself?
For example, we are trying to find out when the start date field was added to our customized Bug work item type.
A field was not there in a previous Increment but we noticed it recently. Just want to find out if there is a date captured somewhere that tells us when it was added or who may have added it?
Unfortunately we cannot get the information from VSTS for now. No date or history included from the retrieved process information via REST API.
However there's already a user voice submitted here to suggest the feature to add Activity Log to VSTS to track user accesses, you can go and vote it up or submit a new one to suggest the feature again to achieve that is future release.
For now as a workaround we suggest that you can ask the team members to add corresponding comments in description area after completing the customization for the process... Thus you can track the history of the customization...
In VSTS (now Azure DevOps), multiple updates can be pushed to a pull request (PR). You can compare any update with its previous update, and you can compare a rolled-up view of all updates with the original code before any changes were made. But how do I compare two arbitrary, non-sequential updates?
My scenario is that a PR has had quite a bit of back-and-forth with a total of 8 updates pushed. I last reviewed update 5, but now 3 more updates exist. I don't want to review 6-5, 7-6, 8-7 or all updates, I just want to review 8-5. How do I do that?
A workaround (in the absence of any user interface to configure two non-sequential updates to be compared) is to edit the iteration=xxxand base=xxx query string parameters in the url, e.g.:
https://xxx.visualstudio.com/xxx/_git/xxx/pullrequest/123?iteration=8&base=5&_a=files
This updates the UI as shown below:
I discovered this because I received an automated email from VSTS notifying me about the latest pushed updates. The email included a "View pull request" button. I clicked the button which took me to the PR in VSTS (I think to the Overview section). There was a notification banner towards the top of the page with a link about comparing update 5 with update 8 which I had never seen before. This sounded promising, so I clicked the link and it took me to the Files section and showed the differences between update 5 and 8 which is exactly what I wanted!
However, subsequent visits to the page (or clicking the "View pull request" button in the email again) don't show that link again, and I can't find anywhere in the UI that lets me define the two updates to compare. So this seems like a one-time opportunity. Miss it, and it's gone forever. I'd still like to know if there's a way to define two non-sequential updates to be compared in the UI, however, the poor man's url hack is a viable workaround for now.
My Requirement is like Build in a process to lock a component during content development or updation.
For example, Vivek can still publish a page with OLT update while another author is updating another component in the same page. The previous version (that is not being updated) will be published along with vivek’s updates.
Since the User group is large & we have frequent updates we can't go for Pagelevel lock(multiple user will be working on the same Page).is der any Possible way to achieve this?... i hav tried the "FieldEditlockMode" but not works for me,am using AEM 6.1
Thanks
AEM Launches may satisfy your requirements, allowing your authors to edit components for future production releases without affecting an immediate release. Here is the documentation for 6.1:
Launches
Creating Launches
Editing Launches
Promoting Launches
We're looking for a solution on how to best deal with the situation where multiple authors are working on the same page. If the first author pushes in the content, the second should have a way to merge it when he tries to publish. Launches appears to be a way to take care of this but it doesn't seem to be handling content merging. Is there any way an author can view the diff(and or do merge) of the content that might have been pushed by another author while they were working concurrently ?
Please help with any pointers.
Page modifications happen in real time to the underlying structure. They also happen at as small a level as possible.i.e. If you go into a text area and modify the text there, the text node is changed on the server, you aren't saving the entire page.
The only way that person A could interfere with what person B is doing is if they were working on the exact same area of the page. Which, honestly is a process issue. I say this because the answer to your question is that there is nothing out of the box to handle this type of scenario and if you are on 6.0 or higher and looking at the JCR3. JCR3 handles this far worse than the older version did. Last time I checked it didn't support nodes at all
Adding to what Bailey said, AEM OOB allow multiple users to edit same page in real time, though if multiple users are working on same node will be a reason of conflict. Such cases can be managed by defining a process like:
1. Take a lock of page and edit page or
2. Create versions of page and publish versions
I'm working on a project that's got a great JIRA setup and awesome buy-in of everyone for the agile development process. The issue I'm having is that tickets stack up in code review. I'd like to be able to see who code reviewed what, much like I can see who has closed out which tickets.
I know that metrics are there to be used for good and not evil, so I want to do this to ensure that people spending time code reviewing are properly credited instead of that time not being recognized at all.
Currently, everyone who does code review assigns themselves to the ticket (which is unassigned upon being placed into the "Ready for Review" workflow state), so at some point there is a record of them working on it. Is this a good way to track the reviewers and is there a way to get aggregate information this after the fact? If not, is there a better way of representing this information in JIRA?
Thanks!
A simple solution would be to add a custom field called 'Code Reviewer' of type select a user. You would be able to search on that and report on it.
You could workflow it so that when the issue is transitioned out of your 'Code Review' status a window pops up containing only the "Code Reviewer' custom field to be completed.
What you need to do:
Create a new custom field - this is done in the 'Issues' configuration menu. Ensure your custom field uses the 'select a user' type.
https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field
Create a new Screen - this is also done in the 'Issues configuration menu. On your new screen you need to make sure that the only field that is visible is your new custom field.
https://confluence.atlassian.com/display/JIRA/Defining+a+Screen
Edit your workflow. Find the transition from out of 'Code Review' and associate it with your custom screen.
https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
The result will be that when a user transitions out of 'Code Review' they will have the custom screen pop-up. They can then select the name of the person who did the code review and this will be populated in the custom field.