I see that there are Slate and Workshop in the Foundry platform. May I know real business cases where we can use Workshop and Slate? How are these different and where can these best fit? can anyone shed some light on this?
How is Workshop different from Slate in Foundry?
3.1k Views Asked by Ram D At
1
There are 1 best solutions below
Related Questions in PALANTIR-FOUNDRY
- MySQL Select Rank
- When dealing with databases, does adding a different table when we can use a simple hash a good thing?
- Push mysql database script to server using git
- Why does mysql stop using indexes when date ranges are added to the query?
- Google Maps API Re-size
- store numpy array in mysql
- Whats wrong with this query? Using ands
- MySQL-Auto increment
- show duplicate values subquery mysql
- Java Web Application Query Is Not Working
Related Questions in FOUNDRY-SLATE
- MySQL Select Rank
- When dealing with databases, does adding a different table when we can use a simple hash a good thing?
- Push mysql database script to server using git
- Why does mysql stop using indexes when date ranges are added to the query?
- Google Maps API Re-size
- store numpy array in mysql
- Whats wrong with this query? Using ands
- MySQL-Auto increment
- show duplicate values subquery mysql
- Java Web Application Query Is Not Working
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Generally, your first choice should be to reach for workshop. Workshop is much more "on rails" than slate, which means the resulting applications are much more maintainable and easier to understand and customize.
Workshop can be thought of as a flexible ontology-based "interactive dashboard maker", where you position and glue together widgets (possibly with some glue code), all of which display or interact with ontological objects (i.e. the objects you see in object explorer.)
Slate is a much more general tool, and you can think of slate a little more like a WYSIWYG HTML designer. It allows you to make fairly arbitrary pages that query arbitrary APIs and data sources. This sounds more powerful, but it's also a much more complex model and things can get messy very quickly.
Workshop is the newer tool, and in a way is better integrated with the foundry platform -- since it interacts with objects (ie allows you to let the user edit objects), knowledge is captured directly and with no delay in the ontology, and other users can directly benefit from it. Since it's integrated with the ontology, it also understands how to meaningfully present data, rather than just showing the users rows and columns.
This means with workshop you can realize quite a few workflows without having to write any code at all, such as inbox-style triaging workflows (alerts / work-items being surfaced in a users inbox, who can then send them on to other users or close them out, etc.) Here's a quick example you could set up in probably less than half an hour, assuming the data is in place:
Slate is a much older tool (it predates foundry) which makes it more powerful in some ways, but if you want to enable users to capture knowledge in slate, you will need to do something more custom like write back to a postgresql database or similar, so it's a lot less "native".
Hence my recommendation is to always consider using workshop first. If you have a workflow that's almost possible to implement in workshop, but there's just some small missing feature, I'd recommend to talk to your palantir contact, as the workshop development team would likely be interested in enabling this workflow in workshop.