Hi Alison 

For the rest of us, can you summaries what the issue is? As I have a demo CRM system and hadn't noticed the issue. Don't know if I'm missing something or the problem only appears in certain situations. 

Within Sage CRM 2025 R1 the Edit Workflow button does not work as expected when looking at a workflow.

The workflow is still enabled and cannot be edited after selecting the Edit Workflow button.  As the page is missing the list of rules some action has taken place so Sage CRM is not ignoring the button press.

Whilst the workflow itself appears to be working as expected not having the ability to take a workflow offline and edit it is a significant issue.

This issue seems to occur with both fresh installations of Sage CRM 2025 R1 and upgrades to Sage CRM 2025 R1. 

Within Sage CRM 2025 R1 the Edit Workflow button does not work as expected when looking at a workflow.

The workflow is still enabled and cannot be edited after selecting the Edit Workflow button.  As the page is missing the list of rules some action has taken place so Sage CRM is not ignoring the button press.

Whilst the workflow itself appears to be working as expected not having the ability to take a workflow offline and edit it is a significant issue.

This issue seems to occur with both fresh installations of Sage CRM 2025 R1 and upgrades to Sage CRM 2025 R1. 

Awesome cheers for that, I will keep my eye out for this happening

My assumption is that this is an issue with the software itself and that this issue can be replicated by everyone within Sage CRM 2025 R1.  If anyone can edit the workflow within Sage CRM 2025 R1 then I would be very interested.

Mine is OK which is why I was asking (v2024 R2 to v2025 demo system)

Edit: I stand corrected, I do have the issue mentioned. If I go into the database and disable it there I can go back and edit the workflow

I have just spoken to a member of my team who performed an upgrade yesterday (from 2024 R2) and can confirm he experiences the issue Alison has raised.

Thankfully it wasn't a production upgrade.  He has already passed it across internally to one of our developers to see if there is a workaround

Not sure if my edit will trigger an update, so will reply again here. Edit the database directly by turning off the Workflow, then edit it as normal through CRM

You will also need to enable it via the database as well it appears

fyi: I'm in US, working on a new CRM install, editing an existing workflow which was installed via Component Manager.  I've done extensive editing and not seen any such problems.  Hopefully I'm not jinxing myself in posting this, lol.

When the workflow was imported into Sage CRM 2025 R1 via the component was it set to be inactive?  Have you then enabled the workflow and then attempted to edit it?

It seems that if a workflow is in the edit state before the upgrade then it will remain in the edit state after the upgrade.  However, as soon as the workflow has been enabled it is not possible to edit that workflow again.

It was some 2 months ago when the component was first installed, so I don't recall for sure but I believe it was enabled when installed.  Since then I've disabled it, edited, saved, re-enabled and tested numerous times, never a problem.  The only other thing I'd say is that it's going against a custom entity.  Not sure if that's relevant or not.

Well sure enough I've just now encountered problems with this workflow. It sounds like a different issue and so I'll be logging this with CRM Support in North America today. The issue is with a Global step. The Valid script generates this error: "This workflow rule is not valid anymore, the record may have been progressed by another user". This error flashes on the screen very briefly and then the JobSummary,asp page is redisplayed. The workflow step itself is never shown. Here is the valid script but again, this does sound like a different problem.

var Stage = CRM.GetContextInfo("jobs","jobs_stage");
var QualifiedDate= CRM.GetContextInfo("jobs","jobs_projqualdate");
var RefusedDate= CRM.GetContextInfo("jobs","jobs_projrefuseddate");
Valid = (Stage != null && Stage =="Startup" && (QualifiedDate == null || QualifiedDate == "") && (RefusedDate == null || RefusedDate == ""));

Alisona, Matthew and all, this is embarrassing but it turns out I was on 2024 R1 after all.  Sorry about that.