I am using an IEM 9.2 Console (IE 10) on my local machine to connect to a remote server.
Whenever I do a local build (deploy my local changes in RTC to the remote server and reload the Server Automation dashboard, all the steps (fixlets) in all my Automation Plans, get this message: “You can not change details for this step because the source is unavailable.” displayed above the step/ fixlet names.
However, this does not happen for two of my colleagues who are similarly conected to the same Remote Server.
I have verified that all my changes a being deployed to the remote server correctly.
You’ll see a “***You can not change details for this step because the source is unavailable.***” message displayed when the underlying fixlet of a step no longer exists on the system.
One of the design features of an automation plan is that it does not require the original fixlet to exist on the system in order to be able to run the plan - the plan itself stores a copy of the selected fixlet action at the time the plan is created.
When the underlying fixlet is deleted however, if (for example) that underlying fixlet defined multiple fixlet actions (e.g. “Action1”, “Action2”, etc.) it just means that we can’t come back to the plan later and change which action in that fixlet we want to run in our plan (since it no longer exists). The plan only stores the action selected at the time of creation, and if the underlying fixlet disappears at some time after that, then you’re left only with the action selected at plan creation time, and you see that message appear.
The the site of the original fixlet of a step is determined by the site-url attribute in the <fixlet> or <baseline> element for the step in the plan XML, so I suspect this is probably out of sync with the server you’re running against. I’d check that first.
I’ll skip commenting on the points related to local builds, RTC and changes being deployed as these are only internally relevant to the dev team (and won’t be of any significance to other readers of this post).