Approval process for new entries

Hello,

Thank you for the suggestion, this is an interesting idea. We have opened a ticket.

Regards,

HI Hubert,

thank you!

KR
Max

Hi Hubert, is there any update aviable?

KR
Max

Hello,

Nothing new for now.

Regards,

Hi Hubert, any update?

Hello,

Unfortunately, we haven't started working on this. We are monitoring this thread for activity from our community, as this is a big factor as to how we prioritize our upcoming features.

Regards,

Hello,

We discussed this internally and we were wondering, would adding a new status like "To be validated" be a good workaround for your workflow? It would be much quicker for us to implement this and it could still achieve what you desire.

Regards,

Hi Hubert,

sounds like a perfect solution! I do not know if it is possible to add a widget to the dashboard "entries to review" and kind of a functionality that the entry can not be used or opened.

Regards,
Max

Hello,

Thanks for the feedback, I have opened a ticket. I have noted to add a dashboard widget for this—we already have one for broken entries (which is another status), so it would make sense to have one for this as well. We will also make it so this "to review" status will work like the "locked" status, which means it cannot be opened by non-administrators.

Just a few additional questions so I can be sure what we offer works for you:

We currently don't have a way to set the status when creating an entry. There's a few possible solutions we could go with to solve this:

• We could add the status as a template setting
  • If your users create entries through templates, then those entries will already have the correct status
  • You can enforce the creation of entries through templates when a template is available for this type of entry, so you can enforce that any new entry created will have this status
• We could allow editing the status when creating an entry
  • This would require your users to set the status manually.

Basically, knowing whether you need a way to enforce this status is important to you, or if simply having the possibility to set that status is good enough, can change the way we go about this solution. I think adding it to the template settings is the easiest for us to do.


What datasource are you using? Devolutions Server, Hub, SQL Server?

If you're using SQL Server, then it's possible we'll be able to add this quicker since we won't need to synchronize with our other products as tightly.


Regards,

Hi Hubert,

the solution sounds great. The template idea is great just two minor questions:

• Could it be possible to set the status as a vault setting for all templates?
• Could it be possible to set the status after the entry creation through a script?

We use Devolutions Server as datasource.

Regards,
Max

Hello,

Thank you Max for the additional information.

For your two questions:

> Could it be possible to set the status as a vault setting for all templates?
We will discuss this internally to see if it would be the best solution, but at first glance, it doesn't seem like a bad idea to have a "default status" setting on the vault. This setting would automatically force created entries in that vault to have this status. This could also work without even the involvement of templates, as any entry would be forced to have this status if you configured this setting.

> Could it be possible to set the status after the entry creation through a script?
You would have to run the script manually, but our Powershell module should already support this for other statuses, so it should automatically work with this new status. You can get and set the status with the Get-RDMEntryStatus and Set-RDMEntryStatus methods.

Regards,

Hi Hubert, first solution would be perfect!

We've added this information to our internal ticket and we will see if we're able to add this to an upcoming roadmap.

Regards,