What's the Difference Between a Sequential Identifier and a Random ID When Protecting a Public Form?

In Jestor, a sequential identifier follows a predictable order (1, 2, 3...), which lets someone try to guess other records on a public form; a random ID instead generates a pattern-free code, making that kind of improper access much harder.

Why this matters on public forms

Public forms used to update a record, like confirming an appointment via a link, become vulnerable if the identifier used in the URL is predictable. Someone could swap the number in the URL and access someone else's record.

Comparing the two types of identifier

Sequential ID: easy to understand internally, but predictable to outsiders
Random ID: generated with no sequential pattern, making guessing harder
The random ID can be customized with fixed text, letters, and numbers
Only the random ID is recommended for use in public form links

How to use a random ID to protect a public form

Create a random-ID-type field on the process's table
Customize the format if you want, with fixed text and random characters
Use that field, instead of the title or a sequential ID, in the public form's URL
Share the link — it now depends on an unpredictable code

Process automation with better access security

Using a random ID instead of a sequential one is a recommended security practice within process automation in Jestor, especially for flows that rely on externally shared links.

Table Summary

Format	Predictable?	Recommended for public forms
Sequential	Yes	No
Random	No	Yes

Video Tutorial: Step by Step

Video: New Field: Random ID — video tutorial showing this feature in practice, right inside the Jestor interface.

Frequently Asked Questions

Can the sequential ID still be used for other purposes? Yes, it's still useful for internal identification, it's just not recommended for public links.

Can the random ID be customized with fixed text? Yes, you can combine fixed text with sequential and random characters.

Is this field available on every plan? Yes, the random ID field is available on every jestor.com plan.

Get to Know Jestor

With Jestor, you can automate workflows, connect different areas, and build internal systems your way — all without code and with AI support. Check out Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize