I have an request data action in nintex workflow, am unable to configure that action because of the disability of the ribbon which consist action,task reminder etc. how can i configure that action or is there any replacement for that action.
If you're using a browser other than IE it can cause this effect.
I've just had the same issue when trying to edit the Nintex workflow in Firefox.
When I switched to IE it worked ok and was once again editable.
I hope that this helps you.
Related
I made some changes to Authorization URL and Token URL in Accounting Linking. After that when I enable Test l, the action with [test] prefix didn't appear under Home Control section in Google Home app. The app is logged in with the same account as the account which I used to create the action. To add up, the action is already being deployed in production. I'm facing this issue when I updated the Account Linking settings and enabled it for Testing. I've also tried undeploying the previous version of the action. But still it didn't appear in the Home Control. Due to this I can't submit my action for review.
Help me out to fix this . Thanks in advance.
Once your Action is deployed to production, the project will no longer reflect console changes to the test agent until those changes are submitted and reviewed. The recommended way to work around this constraint is to create a second project in the Actions console that you can use to test/validate your change.
When you're ready to submit the updates to production, you can follow the steps outlined to updating your existing production project in Launching your smart home Action.
I have completed the overview section and finally was trying to publish my actions but whenever i click create a release button it does not show anything . I am struck on this. Is this server error or something else?
Finally, I was able able to solve this issue. The problem was causing due to a Ad blocker.
I am developing a simple application using ADF comes with basic CRUD operations (create, read, update, delete). In this case, as you can see, I have dragged a link to the 1st column which is highlighted in yellow.
So whenever I deploy it and click that, it is supposed to redirect me to the Edit page where client will allow to make commit:
I did make sure the Action of link is associated with the Edit page (as highlighted in yellow above). However, the link wouldn't redirect me anywhere, no response.This is the unbounded task flow:
Okay so I have found out the solution. Due to the default setting, the application will be deployed on IE and this message will prompt out. As you can see, the message is mentioning about browser's compatibility. My IE is version 11.6, I'm not sure what's the issue here since my IE is kinda latest version but this message still pops out and affects the redirect link from working. However, simply copy the application URL to Google Chrome and run should fix this issue. Hope this helps in future.
If the two pages in the Unbounded Task Flow, then Add WildCard Control Flow Rule
and connect the two pages with the WildCard.
Or you can use the Popup instead of opening a new page for edit
I have a dashboard in Power BI that shows me all the runs that have failed from Logic Apps, incl their runID. Currently I need to copy and paste that runID into the Logic App Runs UI to filter and then click on it to see the Run detail and find out where it failed.
When I click on a run, the runID is not added to the URL, it's loaded via some javascript. How do I generate a URL that will link to a specific run of a logic app instance?
A workaround for this is to add logging/tracked properties etc so that you will get which action failed directly with the runid, it's as close you will get for now I think.
[Edit] found a solution here:
https://toonvanhoutte.wordpress.com/2018/12/08/navigate-directly-to-the-logic-apps-run-details/
For Logic Apps (Standard) there is currently no deeplink available yet. Though Microsoft has added this to their backlog.
See: https://githubmemory.com/repo/Azure/logicapps/issues/358
Edit
Not official, but I figured a way to navigate directly to a Logic App (Standard) workflow. It is possible that a page refresh is needed after navigation though.
Url: https://portal.azure.com/#view/Microsoft_Azure_EMA/WorkflowMonitorBlade/id/%2Fsubscriptions%2F**subscription-id**%2FresourceGroups%2F**resource-group**%2Fproviders%2FMicrosoft.Web%2Fsites%2F**logic-app-name**%2Fworkflows%2F**workflow-name**/location/**location**/resourceId/%2Fworkflows%2F**workflow-name**%2Fruns%**run-id**/runProperties~/%7B%22waitEndTime%22%3A%22%22%2C%22startTime%22%3A%22%22%2C%22endTime%22%3A%22%22%2C%22status%22%3A%22%22%2C%22correlation%22%3A%7B%22clientTrackingId%22%3A%22%22%7D%2C%22workflow%22%3A%7B%22id%22%3A%22%22%2C%22name%22%3A%22%22%2C%22type%22%3A%22%22%7D%2C%22trigger%22%3A%7B%22name%22%3A%22%22%2C%22inputsLink%22%3A%7B%22uri%22%3A%22%22%2C%22contentSize%22%3A0%7D%2C%22outputsLink%22%3A%7B%22uri%22%3A%22%22%2C%22contentSize%22%3A0%7D%2C%22startTime%22%3A%22%22%2C%22endTime%22%3A%22%22%2C%22originHistoryName%22%3A%22%22%2C%22correlation%22%3A%7B%22clientTrackingId%22%3A%22%22%7D%2C%22status%22%3A%22%22%7D%2C%22outputs%22%3A%7B%7D%2C%22response%22%3A%7B%22name%22%3A%22%22%2C%22outputsLink%22%3A%7B%22uri%22%3A%22%22%2C%22contentSize%22%3A0%7D%2C%22startTime%22%3A%22%22%2C%22endTime%22%3A%22%22%2C%22correlation%22%3A%7B%22clientTrackingId%22%3A%22%22%7D%2C%22code%22%3A%22%22%2C%22status%22%3A%22%22%7D%7D/isReadOnly~/false
I have an EPiServer project which is using the sequential workflow to validate content changes. This works fine, however we have a slight issue where content reviewers are just clicking Publish when they are happy with an editor's work. What they should be doing is using the workflow task window and indicating their approval through that.
To enforce this behaviour I would like to disable the Publish button in the content editor under certain circumstances (i.e. when there is an outstanding workflow task linked to the current page).
Does anyone have any ideas how I can do this, or even an alternative solution to the problem altogether?
Actually, I think you may want to revisit your workflow logic.
If a user with publishing rights publishes a page: that should be considered an approval. You could easily hook up to the Published event to see if the page is part of a currently running workflow.