Current Functionality : When we create a model from Revision Tag it creates the model within the same workspace
Idea : Ability to Select the Workspace and creating a model from revision tag in the selected workspace.
This would be incredibly helpful with larger models when it becomes impossible to create a model given its current workspace capacity constraints, even when another workspace is available that has available space.
Yes please, we seek to align our models to the appropriate workspace based on lifecycle so the current process creates an odd workflow where were creating the model from revision tag in DEV workspace only to delete it later once it is imported to PROD workspace. Would be great to have a more robust set of options when creating model from revision tag.
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: Applying things like bps is great but would be great to not have the space between number and item. For pre-defined ones such as %…
Currently Templates can only be run on a certain day of the week or selected date of the month. It would be great if it can have more options to trigger workflows
Before we start, here's a quick description of what are simple lists. Then, I will share how each level in a simple list can be flagged. Simple lists contain list items in a single list with a parent/child hierarchy. For example: It's often tricky to apply logics to this list because you can only add data to child list…
