I would like to share my experience with Nintex Forms Web Request Control . It's a great Form control that everybody loves to use. However, I tried to do complex tasks based on that control and that is when it’s boundaries were revealed. In this post, I will explain what my objective was, how this control limited me and how I got around its limitations. Before that some nice things about this control Advantages This opens up the way to fetch the data from external data sources via HTTP protocol. Not only it provides the comfort of not having to write ajax code but also deals with the CORS issue that every ajax code has to face. How does it overcome CORS? Because it doesn’t request the external web service from the client/browser but rather requests the Nintex REST service ( /_vti_bin/NintexFormsServices/NfRestService.svc ) that is local to the current domain. Apparently, Nintex REST service does the talking with external web services behalf of the web request control. Amazing! Isn...
Are you looking to remove Access Package User assignments programmatically? You have come to the right place. I will walk you through the steps to remove a User assignment from the Access Package. Before we get into the procedure, I assume that you have an understanding of the following items. If not, please follow the links to learn. Azure Entitlement Management Microsoft Graph API for Entitlement Management Alright, straight to the point. How can I remove the user assignment? All you need is an A ssignment id . That's it. Use the below Graph API endpoint using the HTTP POST method with a request body as provided below. Make sure that you are feeding assignment id in the body. Http Method: POST Endpoint: https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentRequests Headers: content-type: application/json Body: { "accessPackageAssignment" : { "id" : " <<assignment...
Comments
Post a Comment