Publish it as an Application

Transcript

Now you’ll give your whole team the Exceptions Desk, with a safe way back. You’ll check each version as the people who’ll use it, then make it live.Give your team one place to open the app you built. In Athena, that place is an Application. It gets its own link, its own versions and its own sharing. Open Create new, and pick Application. Name it Exceptions Desk, and click Create Application. It starts empty. The Deployment tab tells you how to fill it: from a chat. Next you’ll bring your app over, and publish a version you’ve checked.Bring your app over with one request. Use your main chat with the Applications toolkit, and mention the new app. Ask it to copy your app from your Computer. You describe what you want, and Athena does the copying for you. Only the app comes across. Your Computer keeps working as it was. Wait for Athena to confirm the copy arrived, and everything it needs to start is there, before you go on.Try your app safely before your team sees it. Ask the chat to stage a version for review. Nothing live changes. On the Deployment tab, the new version waits under Not deployed yet. Open its preview, and run the exceptions check once yourself. Then copy the link for the people who’ll test it with you.Make sure Sam can use it, and nobody else can. Share the Application with Sam, with view access. Click Share. Sam now appears under People with access. Sam opens the preview, signed in as himself, and the app answers him. Now try someone you didn’t share it with. Priya is signed in, but she gets Access denied, and is told to ask the owner. Sharing the app doesn’t share Freight Desk’s sources or the tracker. Those keep their own permissions.Put the version Sam tested in front of everyone, and keep a way back. On its row, choose Deploy this version. Confirm with Deploy, and the version Sam tested becomes the live app. Later, version two goes out with a problem. Find version one, and choose Roll back to this. Confirm. Your team is moved back to version one as soon as it’s ready. Version one is back on top, marked Live. Every version you’ve published stays in this list, so you can always go back.Quick check. Sam tested version one. What do you make live? That same version. Choose Deploy this version on its row.Here’s how a finance team uses this. Their builder gives the whole team one close checklist. A reviewer tries each change with their own account first. Then that exact version goes live. When a change misbehaves during close week, the team rolls back to the last good version, and keeps working.Try it. Paste this into a chat that can reach your Computer. Look for a Staged card, then a row under Not deployed yet.

​

Before you start

Upload these files from the Northwind starter kit: Lesson 18/Disputes tracker.xlsx, Northwind dispute SOP.pdf, Northwind exception-review checklist.pdf, and Workspace setup.txt. Build Exceptions Desk in lesson 18 first. Ask your admin for Application publishing, version previews, and enough capacity. If publishing is unavailable, watch that step; if previews are unavailable, skip preview testing. Share the agent, procedure, sources, and tracker separately with testers. Uploads do not create published versions or recovery history.

​

Steps

​

Try it

Copy my Exceptions Desk app from my Computer into this chat, then stage it as a version for review. Don’t make it live.

Look for a staged version card and a row under Not deployed yet.

​

Next

Return to Athena 101. More lessons coming.