Application Lifecycle Management for Nintex Solutions
Download as PPTX, PDF2 likes519 views
The document details the deployment process of Nintex solutions and workflows for leave requests in SharePoint. It includes commands for activating features, publishing workflows and forms, and confirming successful deployments. Additionally, it references several resources related to SharePoint development and team collaboration.
Application Lifecycle Management for Nintex Solutions
- 3. Territory Manager – Middle East, North Africa & Turkey Author, Blogger, Speaker
- 10. Adding solution 'ix1.wsp'... Deploying solution 'ix1.wsp'... Activate Features: Activating feature ‘Leave Request' ... Run Post-Deployment Command: All Nintex Features have been activated Successfully Publishing Nintex Workflow Leave_Approval_by_Manager to Leave Request Published workflow to Leave Request --> True Publishing Nintex Workflow Leave_Change_Approval_by_Manager to Leave Request Published workflow to Leave Request --> True Publishing Nintex Form to Leave Request Published form to Leave Request --> True All Nintex Workflows & Forms have been published Successfully ==== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==== ==== Deploy: 1 succeeded, 0 failed, 0 skipped ====
- 13. Check in to Team Foundation Server
- 17. Check in to Team Foundation Server
- 20. Check in to Team Foundation Server Test execution
- 27. Check in to Team Foundation Server Test execution
- 31. Automated deployments DEV QAINT PRODTFS RM Server
- 32. DEV QAINT PRODTFS Full traceability RM Server
Editor's Notes
- #12: Show the Deployment Process from Visual Studio Explain the Scripts
- #32: One major benefit of the new Release Management Server for Team Foundation Server 2013 is that it provides all the automated deployment goodness we were discussing earlier.
- #33: Finally, the whole process is recorded so that you can enjoy full traceability throughout the process. This is extremely valuable in scenarios where there are strict compliance requirements for legal or other reasons.
- #34: Release Management Server provides valuable insights into the entire release process. Armed with relevant and timely information, managers can achieve greater efficiencies by monitoring for continuous improvement. For example, you can keep track of the trend in releases, the amount of traffic in the release pipeline, any possible bottlenecks, and even get performance insights.
- #35: When something fails during the deployment process, it can often be difficult to track down exactly what went wrong. And even once the issue is discovered, there is often a lag in communication for letting other people who what happened. With Release Management Server, there is much greater traceability and transparency for the entire process.