Creating a Project¶
How to create a project and the choices you make while doing it.
Creating the project¶
In the Project List page, use the New Project pane to start creating a new Project. Specify the basic details and then click Create Project.
Project Name: Descriptive identifier (e.g., “Finance BizTalk Modernization”)
Team: Who is responsible for this work
Description: What this project includes and why it exists. This one is marked (optional)
NOTE: a Project name has to be new within its Team. Re-use one and SLIM refuses it, naming the Project that already has it, rather than quietly creating a second Project with a near-identical name. Two different Teams may each have a Project of the same name.
NOTE: if you are not a member of any Team, the New Project pane is replaced by a message telling you to contact an administrator. See Choosing the team below.
You are now in the Project Home Page and need to define the scope of your Project and how it will run. Everything below is on that one form, and you submit it all together.
Upload Platform Export¶
Use the drag and drop zone to upload your selected Export file, or click the zone to browse for it.
NOTE: the file selector filters for .isx and compressed files, so if your Export file is in another format, simply zip or compress it and it should become selectable. Uploading an Export covers the accepted formats, and what to watch for if you drag a file in rather than browsing for it.
Choose Migration Mode¶
The Migration Mode determines whether you want the modernization process to run automatically, or to stop after each Stage. Automatic is preselected and marked Recommended.
For the first few cycles, running Step-by-Step allows you time to assess the outputs from the early analysis Stages before generating any SnapLogic assets.
Once you have an understanding of how SLIM capabilities such as additional instructions can help refine and restructure the generated assets, Automatic mode can be a great time saver.
Step-by-Step mode ensures a human presence at every Stage, and iterative processing to allow validation for completeness and accuracy before moving forward.
NOTE: if you later choose to Replace Export, SLIM switches to Automatic mode. To get back to working a Stage at a time, use the Stop button on the executing Stage Page: interrupting a run also returns the Project to step-by-step working. See Uploading an Export.
Agent Model¶
SLIM uses AI models to do the work of analysis and generation. The Agent Model panel is where you choose how much capability to bring to it, and it holds two settings: the Model and the Reasoning Effort.
The Model picker lists the models available to you, each with a note on its relative speed and cost. One is preselected as the sensible default. Picking a more capable model raises both the quality ceiling and the cost; picking a cheaper one lowers both.
Your choice sets a ceiling for the whole Project rather than a fixed setting. Simpler pieces of work may be handled by a cheaper model, but nothing SLIM does behind the scenes reaches for a costlier one than the model you picked.
NOTE: the model and the effort level are fixed when the Project is created, and no screen lets you change them afterwards. Choose deliberately - see Project Settings.
Reasoning Effort¶
The Reasoning Effort setting controls how hard the agent thinks before it acts. Higher effort improves quality on complex integrations, at the cost of more time and a larger token spend.
Unlike the models it works alongside, effort is not something you pick per Stage: the level you set here applies to every Stage in the Project.
Between them, the two settings are your main control over what a Project costs. Reserving the more capable models and the higher effort levels for genuinely complex work, and letting straightforward integrations run cheaper, is how experienced users keep the overall spend in proportion.
Global Prompt¶
The Global Prompt is one way to add extra instructions to the Project. Unlike the per-Stage instructions, it applies to all Stages in the modernization process.
This is helpful if there are any identified constraints that should apply across all Stages of the process, such as naming conventions or the SnapLogic project space to deploy into.
You are not committed to what you write now: the Global Prompt can be edited at any time from the Project Home Page.
Each of the three Stages that accept their own instructions - Export Analysis, Integration Analysis and Pipeline Generation - carries its own panel on its Stage Page, named after the Stage. Instructions you put there apply to that Stage alone.
NOTE: Design instructions or influences should never be included in the Global Prompt as this could add bias to the non-SnapLogic oriented Stages, such as the Integration Analysis Stage, or generate a less independent Functional Representation of the integration logic in the initial part of the Pipeline Generation Stage. Design material belongs in Supporting Files, which SLIM deliberately keeps away from the analysis Stages.
Supporting Files¶
At times, SLIM is brought into situations where some modernization efforts have already begun manually, with generated Design directions or documentation already approved.
Assets that already contain approved design parameters can be uploaded to the Project and used to influence the Pipeline Generation to align with pre-determined designs.
Other reference documents can also be added to the Project to assist with expanded context, if there are situation-specific constraints that need to be accounted for.
The distinction between the two matters, and SLIM asks you to make it: for each file you attach, say whether it describes the target SnapLogic design or the source workflow. Design material reaches Pipeline Generation only. Reference material is available to the analysis Stages as context. That separation is the reason an approved design cannot color SLIM’s reading of what your integrations do today.
You can attach several files at once, and add more or re-tag the ones you have later on the Pipeline Generation page. Office documents are converted to a readable form automatically as they are stored.
Diagnostic Logging Toggle¶
For troubleshooting or detailed analysis, use the Diagnostic Logging card and turn on the Enable diagnostic logging switch. It is off by default.
Records what each agent was asked to do, what it did, which files and references it used, how long it took and what it cost
Generates a clear step-by-step audit trail of activities performed by the underlying AI Agents and Skills
Useful when working with SnapLogic Support or investigating issues
Lets you compare one run against another to see what made the difference
Once you have selected the appropriate choices for your Project, click Upload & Start Migration to add your Export file to SLIM.
NOTE: this button starts no analysis: It stores your file and your choices and returns you to the Project Home Page, where Extract Assets is the button that begins the work.
Choosing the team¶
The Team assigned to the Project controls who can collaborate on the contents of the Project.
By default, your personal team is the one selected for any new Project: this limits access to the Project to only you. Other teams are created by your Organization’s Managers to provide wider access options.
Once the Project is created, an Administrator can adjust the assigned team, to broaden or restrict access. There is no control for this on the Project itself, so a Project created in the wrong Team needs an administrator to move it.
Deleting a project¶
A Project can be deleted from the Project List.
In the Tile view, the Delete icon appears in the top right corner of the Project card when you hover the cursor over each card.
In the List view, the Delete icon appears when you hover the cursor over the space to the right of each Project row.
A confirmation prompt will open, naming the Project, and allowing you to confirm or cancel the deletion.
NOTE: deleting a Project will delete all of its assets, so ensure you have downloaded anything you need to preserve via the Project Home Page before deleting the Project. If anything is still running, deletion stops it first.
NOTE: anyone who can see a Project can delete it. There is no separate permission for deletion, so in a shared Team the Delete icon is available to every member.