Skip to main content

Notifications

Announcements

No record found.

Customer experience | Sales, Customer Insights,...
Unanswered

missing activate deactivate buttons on workflow/process

Posted on by 437

I have a workflow (process) where I am the owner.  I am an administrator of Dynamics/Powerapps.  

I could not see this workflow in the classic solution editor using Add Existing.

I can see it in the new solution editor.  So I added it to the solution for the current sprint.

The workflow moves portal created tickets (incidents) to a specific queue.  It works.

When I edit the workflow using the classic editor now, The only buttons on the command bar are  Close and Actions/email a link.

see image below

Does anyone know why this might happen?

pastedimage1678372545128v1.png

all of my other workflows appear thusly:

workflow-having-command-line-buttons.PNG

  • urklnme Profile Picture
    urklnme 437 on at
    RE: missing activate deactivate buttons on workflow/process

    and the answer is......

    I exported the solution to which I added the process.

    in that solution I found the workflow definition for that process.

    I noticed that it had a property named RendererObjectTypeCode with a value of 8181.

    I looked up the entity type code of 8181 SHAZAM!!  Routing Rule

    sysadmin-central.com/.../

    Setting/Service Management/Routing Rule Sets/<process name>

    pastedimage1678460041174v1.png

    the routing rule actually creates a workflow.  this workflow does not appear in the classic solution editor, in the processes tab.

  • Ray Profile Picture
    Ray 1,505 on at
    RE: missing activate deactivate buttons on workflow/process

    Not sure about the reason, but I think there are some things you can check about:

    1. Go to solution page and click Processes, select this workflow and see if the Activate/Deactivate button shows:

    pastedimage1678434918823v2.png

    2. Updating workflow status by Odata API and then check the workflow page to see if the button shows.

    var entity = {};
    entity.statecode = 1; // 1 = Active, 0 = Inactive
    var id = "E03A6A96-857D-4DB2-AF20-BF950D74548D"; // replace it with your workflow id, you can get it from the URL when you open the workflow in the browser
    var req = new XMLHttpRequest();
    req.open("PATCH", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/workflows(" + id + ")", true);
    req.setRequestHeader("OData-MaxVersion", "4.0");
    req.setRequestHeader("OData-Version", "4.0");
    req.setRequestHeader("Accept", "application/json");
    req.setRequestHeader("Content-Type", "application/json; charset=utf-8");
    req.onreadystatechange = function () {
    if (this.readyState === 4) {
    req.onreadystatechange = null;
    if (this.status === 204) {
    //Success - No Return Data - Do Something
    } else {
    Xrm.Utility.alertDialog(this.statusText);
    }
    }
    };
    req.send(JSON.stringify(entity));

    3. Check the console log in browser developer tools, and check about the html for these buttons.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans