Skip to main content
featured-image
featured-image
featured-image

Interfaces (BETA)

We are very excited to announce that today we are releasing the Interfaces (BETA).Feature Description: Interfaces empower users to create and share custom Interfaces effortlessly inside their organization, ensuring the correct information is given to the right people, all without coding. With Interfaces, you can manage an unimaginable amount of processes.Use case (examples):Procurement: Add pipes and databases for visibility of cost centers. With Interfaces, analysts can visualize information of an entire area on one page.IT: You can create a centralized Interface for IT managers to see what’s pending and what’s already approved from access management processes, as well as create a customized page for internal clients to check the progress of their requests and act on it if required.HR: Managers can have an Interface centralizing pending action on recruiting processes, promotions, job movements from their employees, and vacation approval all in one place.Users can create an interface for stakeholders to view and interact with their requests only, even if they are not pipe members using the filter “created by email” is “current user.”Change the permission so that each pipe admin can create Interfaces with their processes (permissions coming soon, stay tuned!)It’s possible to add connection fields inside a record detail so users can view and edit the value on a connected card/record. It works like the record detail itself, so admin users can decide which fields to show in the connection and if they can be edited – making it exceptionally flexible and adaptable to each process.👉🏻Here is an article to help you in this first exploration. For what kind of customers?  Interfaces (Beta) is available for all customers. 🔜 We are already developing permissions to Interfaces so you will be able to add more people to customize the Interface and also add users into private Interfaces. As soon as it’s delivered, I’ll let you know.😉Feedbacks are welcome! 😀👇🏼

featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image

📢 Overdue alerts for weekday

This new allow pipe admins to have different SLAs for demands on their processes, while maintaining these SLAs accounting for weekdays only.Use case (examples):Purchase process: Applying rules of due date like: Urgent purchases - 5 weekdays, Normal purchases - 10 weekdays; HR request: Applying rules of due date like: Vacation request - must be approved on 3 weekdays, Address update - can be completed up to 5 weekdays;Feature Description:When you turn on the option “Alerts will count from Monday to Friday” inside pipe settings, this will reflect on the 3 types of SLA we have today:> Expired alert (maximum time (SLA) for a card to be finished in the pipe)> Late alert (maximum time (SLA) for a card to stay in a phase) > Overdue alert (limit date for each card to be finished (based on the Due date field))Besides the due dates filled by automation or autofill consider only weekdays, people filling a due date manually won’t be able to select Saturdays nor Sundays. It will be blocked to click on them either on a field (on start form, phases, public form, public phase form) or at the card’s attribute.What was changed?Before, when setting up a relative date automation (or autofill) it would account for all calendar days in any scenario. We also added more contextual help on tooltips when setting this up, to make the behaviors clearer for customers.For what kind of customers? All customer base.

featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image
featured-image