This functionality is provided as a preview
of intended future API capabilities. You are encouraged to use it and report any problems or suggestions using the
Fusion API and Scripts forum.
Because this is a preview of future functionality, there is the possibility that it will change, which will possibly
break any existing programs that use this functionality. Because of that, you should never deliver any programs that use
any preview capabilities. For a distributed program, you should wait until it has moved from preview to released state.
Defined in namespace "adsk::fusion" and the header file is <Fusion/ConfigurationRules/ConfigurationRulesManager.h>
Description
Applies the request described by input atomically. Deletes run first, then reorder, then adds and updates. Non-fatal per-rule problems are reported in the result's issues array; the rest of the batch still applies even when a VALIDATION_FAILED or RULE_NOT_FOUND issue is recorded. Fatal errors (invalid request shape, uninitialised rules pipeline, missing extension entitlement) throw an exception.
Always inspect the returned issues array after a successful call — an empty array means a clean apply; a non-empty array means at least one block silently degraded to a placeholder.
A ConfigurationRulesResult whose rules array contains the post-mutation descriptors for added or updated rules (in the same order as the corresponding input rules); when orderedRuleIds is set, the array also includes the reordered rules in their new order. The issues array is empty when the request applied cleanly.
This functionality is provided as a preview
of intended future API capabilities. You are encouraged to use it and report any problems or suggestions using the
Fusion API and Scripts forum.