Settings and activity
10 results found
-
4 votes
Morgan Moonan
supported this idea
·
-
5 votes
An error occurred while saving the comment Morgan Moonan
shared this idea
·
-
2 votesMorgan Moonan
shared this idea
·
-
14 votesMorgan Moonan
supported this idea
·
-
22 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Morgan Moonan
supported this idea
·
-
7 votesMorgan Moonan
supported this idea
·
-
43 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Morgan Moonan
supported this idea
·
-
10 votesMorgan Moonan
supported this idea
·
-
5 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Morgan Moonan
supported this idea
·
-
5 votes
Thank you for voting on this feature request. Our product team is currently reviewing it and evaluating its feasibility and potential impact. We will keep you updated on any progress.
Morgan Moonan
supported this idea
·
We've discovered another issue with LOVs and portal imports. After delete/import of the workflow data source of an LOV, and the import of portal pages that correctly use the LOV with the workflow, the LOVs are still not updated to the new workflow version. This means that every LOV that uses a workflow data source needs to be reconnected, even after importing an entire portal page that already has the updated LOV and workflow on it. As users we also can't export/import LOVs altogether, so that's why updating them upon import of a portal page that uses it is such an importance. Even deleting the existing LOV, and then importing the new and updated one so that everything connects properly will work.