Automation

OASIS lets your team set rules for work that follows a repeatable pattern. A rule can help tag an item, assign it to someone, or create a case when it needs follow-up. Other rules can support approval routing and recurring reports.

Start with a task you can explain clearly. What should happen, and under what conditions? If the answer changes every time someone looks at the situation, the rule may need a narrower purpose.

For example, a team may want certain incoming items to reach a designated reviewer. Before setting that up, agree on which items belong with that person and what should happen when the rule finds a match. Clear conditions make it easier to check whether the automation is doing the job you intended.

Preview a rule against real records before enabling it. Look at the matches and check for items you didn’t mean to include. A condition that seems specific can still catch unrelated work, especially when it relies on a common word.

After a rule runs, its execution history helps you review what happened. Check that history when an item reaches the wrong person or an expected action doesn’t occur. It also gives your team somewhere to start when a process changes and an old rule needs another look.

AI assistance can help prepare drafts or summaries where your organization allows it. Your team still needs to check the result. Names, dates, and image descriptions deserve particular attention before anyone uses them in a public message.

Automation follows your organization’s approval requirements. A rule should have a defined job, an owner, and a reason to remain active.