Re: Block start/stop processors

[Russell Bateman]

Isha,

Wait, by "lefthand toolbox" are you referring to the process group's 
toolbar start button or to the start button in the pallet at the upper 
left of the page?


Please clarify.

Thanks


On 2/22/24 04:39, Isha Lamboo wrote:

always use the right-click context menu on a process group you want to
stop/start and never use the button in the lefthand toolbox.
Right-clicking the PG also selects it, so you don't have the risk of
clicking stop with no selection.

RE: Block start/stop processors

[Isha Lamboo]

Hi Alexandra,

The workaround we use is to always use the right-click context menu on a 
process group you want to stop/start and never use the button in the lefthand 
toolbox. Right-clicking the PG also selects it, so you don't have the risk of 
clicking stop with no selection.

Removing the operate permission on the main canvas and adding it to all process 
groups is probably the real solution, but a lot of work indeed.

Regards,

Isha

-Oorspronkelijk bericht-
Van: alexandru.d...@orange.com  
Verzonden: dinsdag 20 februari 2024 10:41
Aan: dev@nifi.apache.org
Onderwerp: Block start/stop processors

[You don't often get email from alexandru.d...@orange.com. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

Hello!

My name is Alexandru Duță and I am working at Orange Services Romania.
We are actively using Apache NiFi in our projects and we have a problem that we 
want to avoid in the future. We think that you can help us with that.
It happened for us (the admins), by mistake, to start/stop all the processors 
from the NiFi root page, and because we have over 5000 processors in our 
projects, this bring us a lot of difficulties.
Is there a way to block this kind of requests? We don’t want to do that through 
the permissions, because how I said, we are admins.
We were thinking is there is a possibility of a pop-up page to be displayed 
when this is happening, that will ask for our confirmation or if we can block 
those nifi-api requests.

Thank you in advance for your answer!

Best regards,
Alexandru Duță



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law; they should not be distributed, used 
or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Block start/stop processors

[alexandru . duta]

Hello!

My name is Alexandru Duță and I am working at Orange Services Romania.
We are actively using Apache NiFi in our projects and we have a problem that we 
want to avoid in the future. We think that you can help us with that.
It happened for us (the admins), by mistake, to start/stop all the processors 
from the NiFi root page, and because we have over 5000 processors in our 
projects, this bring us a lot of difficulties.
Is there a way to block this kind of requests? We don’t want to do that through 
the permissions, because how I said, we are admins.
We were thinking is there is a possibility of a pop-up page to be displayed 
when this is happening, that will ask for our confirmation or if we can block 
those nifi-api requests.

Thank you in advance for your answer!

Best regards,
Alexandru Duță



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.