Is it possible to manage Support Management/Cases ...
# sdf
m
Is it possible to manage Support Management/Cases through SDF?
s
Can you say more about what you want to do?
m
Hey @Sean Murphy, I’m basically just looking to consolidate all the settings that comprise our Support workflow into an SDF project. The various Case Types, Isses, Territories, Statuses, etc. When we make changes we can make them in the SDF project or at least pull in changes from the UI and commit this to the VCS. My alternate plan is to create a JSON representation of the various settings and commit that to a VCS project. Doesn’t help deploy changes but it at least creates some type of versionable record of how the Support features are setup.
s
Ok I see, SDF should be able to handle all of that. It is a collection of lists and custom values mostly. If you are having trouble access those in SDF it is likely a permissions issue with your SDF role. Try logging in to the hi using that role and see I’d you can access those properties.
Also I noticed you said you would make the Changes and then pull them into an SDF project. I would recommend that you consider making the changes using SDF, then you do not have to pull the value in.
m
Morning @Sean Murphy, so I’ve spent most of this week trying to find a good solution to this. It looks like the Case system features aren’t “manageable” through SDF. There are no objects to be pulled into an SDF project to manage from. I can manage Case Entry Forms and any custom fields applied to them. But I can for instance find a “list” object that defines Case Types or Case Origins or Case Statuses, etc.
I’ve resorted to creating an SDF project for the Entry Forms and Custom Fields and then defining a file I call
nsconfig.json
with a custom schema for outlining the settings for each of the Case components.
The config file can be manually updated to reflect the current state of the components to track changes over time.