You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our integration implementation create temporary result files that exist in parallel to the files they would replace. Once an integration is complete, a user would want to make those temporary files permanent.
An added complexity may be that in some cases (specifically for scenarios, new custom adoptions), it may be desired to add an additional file instead of replacing an existing one. Some spec on how the user controls this would need to be worked out.
In the case of replacement or addition, there is also a potential question of naming: should the new resources have a new name, and what should it be. This would need to be spec'd out as well.
The text was updated successfully, but these errors were encountered:
Our integration implementation create temporary result files that exist in parallel to the files they would replace. Once an integration is complete, a user would want to make those temporary files permanent.
An added complexity may be that in some cases (specifically for scenarios, new custom adoptions), it may be desired to add an additional file instead of replacing an existing one. Some spec on how the user controls this would need to be worked out.
In the case of replacement or addition, there is also a potential question of naming: should the new resources have a new name, and what should it be. This would need to be spec'd out as well.
The text was updated successfully, but these errors were encountered: