🇧🇷Brazil @marco aurelio rocca

Thank you, @johnv!
I was trying to achieve such a reaction through the Drupal interface, not programatically, and I guess I got that:

1. Workflow status is stored in a workflow-type field on the content-type
2. Node to be automatically transitioned will have this new field value set through a normal "Entity Set Field Value" action
3. Also, a Transition is "found" (and thus will trigger an ECA model) through the "Update Content Entity" event

IT WORKS!!
Thanks a lot (again)!!!

OK, THAT I did not try, really cool!
You fill "field value" with the very present value of the field, which you want to clear... is that correct?
I'll try that in my environment next monday and bring here the result!
Thank you very much!

UPDATE:

• couldnt make the Entity Reference field turn EMPTY,
• letting empty the "field value" did no change it at all, while
• filling it with word "NULL" made it point at the ANONYMOUS user, which is the same as if I had made "field value = 0"
• even then, I DID manage to get it "pointing at nowhere", by forcing something monstrous like "field value = 111111111" (that is, a non-existent User entity)....
• ugly, isn't it? ^_^''
• any better idea?

Sending the model exported, as previously said, and a correction: the trigger is called 4 times...

• "field_atendente" here is an Entity Reference field, pointing to a User
• "field_statusdemanda" here is a Workflow Field, with Workflow module turned on (not Drupalcore's "Workflows", notice), where the workflow state of the node is set.
• "update entity" then is a trigger that tries to detect that a Node has had its workflow-state changed, and react to that in such a way that either a User is comissioned to "take care" of that node OR a User is unset at all, because no-one will take care of that node.
• attached image shows where the specific problem lies: when I try to UNSET the Reference to a User Entity

Hallo, Jurgen, yes I've tried those methods, "Set and enforce clear" too, leaving empty the "Field value" field, with no results. Also, that "Remove value instead" was tried in vain before I read it with more attention and noticed that it is intended for multi-value fields, which is not my case.

This ECA Model where I find such a problem has the "Updated Entity" trigger called 3 times. Could that interfere with anything relevant here? I'll upload the exported model, but it will refer to content types and fields specific to the project, hope it is not so bad.

marco aurelio rocca → created an issue.

Ok, @Jurgenhaas, thank you again for showing my misunderstanding.

All this is really me trying to reproduce Drupal 7's "RULES LINK" funcionality.

I opened an issue on ECA CONDITION module, a few days ago, as in https://www.drupal.org/project/eca_condition/issues/3502923 💬 Cannot have MORE THAN ONE block loaded with EcaCondition? Active , hope I can find some help with that too.

Hallo, sorry for forgeting about that. Uploading the exports made through that page. THere's something there called "export as recipe", but I didnt get how it works so I opted for the simple "export" option.

marco aurelio rocca → created an issue.

Ok, I'll do that, thank you!
Guess this issue might be closed, since it ended up being a mess of "side-quests"... :)

Thanks again!
My tests here still stumble on something weird: will you confirm to me whether I should open this as a different issue? It follows:

1. create new Model, where Event = ECA Block
2. you give it a name
3. you struggle with your conditions and use an action like RENDER: TEXT to give this block some content
4. you go to /admin/structure/block/list/{themname} and find this block and manage to make it show up in some region of the theme
5. you get the block's machine name
6. if your conditions are not fulfilled, you use action = UNPUBLISH CONTENT BLOCK, giving the machine name of the block
7. Things work well, so that the content you want to show up ONLY when those conditions are fulfilled DO show up ONLY under those conditions.
8. you get happy and start it all over AGAIN, with NEW conditions and new content,
9. you end up with 2 or more new blocks, which will go through different sets of conditions and, when those are fulfilled, different contents
10. PROBLEM: THEY INTERFERE WITH EACH OTHER, in such a way that it seems that THE FIRST ONE returning a "disappear!" command, from that "action = unpublish content block", makes ALL OTHER blocks UNDER that failing one to FAIL TOO, making them disappear REGARDLESS of having fulfilled their respective conditions...

Hope I got it well written, sorry if I did not...

Any glance at that?
Should I really take this into a new issue?

ADD:

As I toy around with the ORDER of the many ECA Models (as seen in /admin/config/workflow/eca), it seems that it is the LAST result, among all those models like "ECA Condition ()", that will RULE THEM ALL, making all blocks to "show up" or "not show up"..........

(worse: sometimes EVEN those blocks whose Models which I have DISABLED happen to show up)...

marco aurelio rocca → created an issue.

Hallo, Jurgenhaas,
I've been trying to use that module you mentioned, and it has its own issues... I'll soon add my problem there.

In this present case, my original usecase was "can I manipulate que results of a view, so that a block showing the results of a query might not to show them all, but only those that I manipulate?" I was trying to purge some rows off the result, but I couldnt have the rebuilt list exhibited.

marco aurelio rocca → created an issue.

marco aurelio rocca → created an issue.

As the page called was already /node/[nid], I assumed that this entity was already to be found loaded into some variable that I could get my hands on (maybe using some other Event as a trigger), so that I could avoid loading it "again".

But ok, then!

I used "Controller found to handle request" as the Event, then Action "Request: Get path argument", and it did work.

Thank you once more!

Very nice, @sprucmoose , those are the same fields I found, too! Sorry I didnt come here before.
In case it might help people who come around here, the steps I made to find those fields out where:

• create a Comment, the "normal way", without trying to use ECA (that will give me valid data into the database tables, from where I will be able to take some references)
• Run the ECA model using just that "Create (comment) Entity" action, and try to save it, withoui knowing it better (that will not work, I know, it sucks)
• get to the Recent Messages page, in /admin/reports/dblog
• inspect the error messages found there - some will eventually tell you something like ERROR ... SQL ... INSERT INTO ... and some COLUMN NAME whose absence it is complaining about
• then go to MySQL (this is possible for me only in a DEV environment, or I wouldnt get access to the PROD tables, in my case here), open the databse and search around those tables whose name start with "comment",
• try to find there a column with the same name as that one mentioned in the error message
• in that column name found inside the databse, find the value of the previously created Comment (that you made in "the normal way"
• try to take this value back to you ECA Model, and use the SET FIELD VALUE Action to insert this value to that field

Sometimes you will find out that the name of the COLUMN is not the name of the FIELD, but some of the changes needed to make it work may prove somewhat easy to infer (like turning something_nid into [something:nid]

Wow... that's far more than I would infer... :(

My point, from the very beginning, was to have a Model that does something like
"Hey, cool, this is a NODE page! Give me this node's data in my hand, so that I can use its information to do this or that"...

Is there a simple way to achieve this?

Let me correct my previous text:

... I cant understand how it would have succeeded to get as far as that [current-page:query:supimpa] if no Entity token is loaded in the scope.

Guess this will be more usefull!

i'll clone that huge model and strip it of everything else... then try to understand whether or not it still works, and try to export it into here, again, if you allow me.

That moment, when [current-page:query:supimpa] is checked, is already a third step of the Model, of further yet, after I have already asked for a specific Route (and it seemengly said: "yes!") and after I have asked for a specific NID from the Entity loaded in the page (and it said "yes!")... I cant understand how it would have succeeded to get as far as that [current-page:query:supimpa] is not Entity is loaded in the scope.

Let me bring another shorter version of the Model, soon.

I exported the model, there are many dependencies related to the specific site we have here, hope it helps!
Unsure that the export may be of real use, I tried some screens also!

Is that different from previous versions of ECA? o_O''
Let me describe a situation that works today, running well on production site with Drupal 10.2.7 with ECA 1.1.9:

1. model starts with event = CONTROLLER FOUND TO HANDLE REQUEST
2. from Event to Gateway, the Arrow has a template = ROUTE MATCH, and here I have fields set to give me an answer like: "is this route name ENTITY.NODE.CANONICAL?"
3. from Gateway 1 I have an arrow towards Gateway 2, and this arrow has a template = COMPARE SCALAR VALUES, and there I do have a token equals to [entity.nid], which I compare to a specifica integer number
4. from this on, the model flows

This thing works well today, on PROD site, with the [entity] token being recognized and the "entity.node.canonical" route name being known to the ECA model.

If things have changed about these features, and those pieces of information will no more be available this way, it means I CANNOT upgrade Drupal + ECA version on this prod-site, is it so? o_O"

marco aurelio rocca → created an issue.

That was all great!
Thank you for all your effort, Jurgenhaas!

It worked!
Just not obvious: had a little effort trying to understand which fields were needed, what their names were and what kind of value they wanted to receive. So I opened a MySql interface and compared the tables, fields and values filled by data from a naturally-created Comment (i.e., from the form under a node entity), and then things worked out.
Thank you!

Thank you, @Jurgenhaas, will try that!

marco aurelio rocca → created an issue.

Found: it's in /web/sites/default/services.yml, right??

Marco Aurelio Rocca → created an issue.

It works!
Action triggered by
event = RESPONSE CREATED,
condit = ROUTE MATCH compared to "entity.taxonomy_term.canonical",
Action=LOGS MESSAGE
+ Action = REDIRECT do frontpage.

Navigated to a Taxonomy list of terms, clicked them repeteadelly, log messagens are recorded several times and navigation is redirected to frontpage, not for once only but repeatedly.

Thank you so much!

Thank you, @jurgenhaas!
I'll try that as soon as possible!
If I get it right, would be better to try it after updating to 2.0.x-dev.

Thank you so much for your efforts, @Jurgenhaas!

I made an EXPORT of the last test with trigger = "controller found", and send it here.
I dont know whether it is useful, hope so.
I did not get ahead with the step = "load the entity (i.e. the term) by using the route parameter", because I realized that there, too, that CACHE thing is in effect. So it is in my way again... and I cant figure out why, looking at the Developers Panel :(

What the ECA here exported do:

1. triggers when a "Controller Is Found" action takes place
2. checks whether or not the "Route" used is like "entity.taxonomy_term.canonical"
3. if so, logs a message in the registry
4. redirects towards the FrontPage

But, again, it will only work ONCE PER TERM CLICKED. After that, it'll not work again until a Clean Cache is performed.

So it was already there and I missed it, sorry!!
Thank you!!
And thanks for working on such a module! I am an orphan from RULES LINK! ^_^

Marco Aurelio Rocca → created an issue.

Thanks again for your time, Jurgenhaas!

I could not yet manage to put our site somewhere reachable by you, but I'll try to get that done.

I could use the "CONTROLLER FOUND" as trigger, and in the sequence I used "ROUTE MATCH", set to "entity.taxonomy_term.canonical", and made a redirect action. Thus, I could kind of INTERCEPT all callings to any taxonomy terms, with a REDIRECT action.

But that was just a drill.
The GOAL is to intercept only Term Entities of a specific Vocabulary, where I do have a custom field with non-empty value.

I understand that what's missing for me is a way to grasp the data about that specific Entity, which is called by the '/taxonomy/term/{taxonomy_term}'-like path.

Does that make sense?

Thanks you for your time, @jurgenhaas!
I cannot say that I understood the point, but anyway I tried to figure it out with no success. Drupal installation configured, as far as I know, to prevent caching, with no effect. Tried to use Eca-Cacheabilty, using "Cache invalidate" in a couple of situations... but the interface demands sobre CACHE KEY parameter that I do not know how to provide.

Marco Aurelio Rocca → created an issue.