Loading

Visit Submission Failure — Provider Visit Workflow Issue

Publiceringsdatum: Jul 7, 2026
Beskrivning

When an LSC Workflow is created for an object — for any one Record Type — the managed
package automatically registers the parent object in LifeSciStageObject with
ObjectName = "ProviderVisit" and IsControlledByStagePath = true.
From that point on, the framework treats every Record Type of that object as
stage-path-controlled, including ones for which no Workflow was ever defined.

 

1.The error wording was literal, not metaphorical. "Stage of the workflow" referred to
LifeSciStagePath records in the LSC managed package, not to a generic permissions
concept.
2.'IsControlledByStagePath' is sticky at the object level. Once any Workflow is configured
for one Record Type, every Record Type of that object becomes implicitly stage-controlled
until it has its own active Stage Path

Lösning

1. Review the Provider Visit workflow configuration and set IscontrolledStageValue to false to allow Provider Visit creation at the affected workflow stage. 2. After updating IscontrolledStageValue, validate that Provider Visit creation works as expected and close the case if the issue is confirmed fixed.

 

Configure (or activate) an LSC Workflow / Stage Path for the 
ProviderVisit Record Type in:
Admin Console → Workflow Configuration → Workflow Paths
Alternatively, if ProviderVisit should not be stage-path-controlled at all, set
IsControlledByStagePath = false on the corresponding LifeSciStageObject
row — but note this affects every Record Type under the object, so the per-RT Stage Path
approach is usually safer

Knowledge-artikelnummer

005388591

 
Laddar
Salesforce Help | Article