While an arbitrary partition ID is useful in some cases, in others it is more important that the raw activity ID be readable. For such cases, we should allow users to disable the functionality that hashes partition IDs before putting them in activity IDs.
When the hashing functionality is disabled, a stricter length limit will need to be applied to partition IDs, as well as the same character set constraint as the rest of the identifiers, though the can't be the exact string "arn" limitation will not apply.
While an arbitrary partition ID is useful in some cases, in others it is more important that the raw activity ID be readable. For such cases, we should allow users to disable the functionality that hashes partition IDs before putting them in activity IDs.
When the hashing functionality is disabled, a stricter length limit will need to be applied to partition IDs, as well as the same character set constraint as the rest of the identifiers, though the
can't be the exact string "arn"limitation will not apply.