πŸ‡¬πŸ‡§United Kingdom @alastairworters

Account created on 5 June 2017, about 7 years ago
#

Recent comments

πŸ‡¬πŸ‡§United Kingdom alastairworters

Hello,

I have the same issue with the asterisk not showing when the 'Basic PCA address' field is set to required. Based on the comments above, I have tested with a few different themes and the red asterisk still doesn't appear.

I'm not sure whether it's a webform issue or a problem with the PCA Address and/or PCA Webform module.. so apologies if this should have been posted elsewhere.

πŸ‡¬πŸ‡§United Kingdom alastairworters

I have the same issue. Is there any fix?

Also, when the field set to required, the red asterisk to show a response is needed doesn't show. This issue doesn't appear to theme related as have tested on a couple of different themes but asterisk is still missing.

πŸ‡¬πŸ‡§United Kingdom alastairworters

I have a similar issue with PCA address fields not being populated.

Tested using an export (download) of existing submission data which contains all the data (including address fields), but when I try to import the csv file, there are no destination options for the mapping of the address fields used by PCA...

πŸ‡¬πŸ‡§United Kingdom alastairworters

Thanks.. The patch makes the module work.

πŸ‡¬πŸ‡§United Kingdom alastairworters

Apologies for the large screenshot.. I only meant to show visually what my issue was, however I will follow your instructions from now on.

To answer your question, I am using ECA to create a webform node, referencing from a central webform, rather than creating a webform_submission.

The model I have created successfully creates a webform node. I am also able to pull through the file URL as a token from the referenced entity and can display the url with in a message to the user. However I am unable to pre-populate a text field within the newly created webform node using the token that contains the URL.

Reading through the documentation and watching your tutorials I thought that it would be a case of setting the field value of the new webform entity placing the assigned token holding the file URL into a field within the webform node.

πŸ‡¬πŸ‡§United Kingdom alastairworters

Thank you Jurgen,

I appreciate you taking the time to let me know your thoughts on working with Workflows and various ways they interact with ECA, and also your suggestions on how to find a solution for my particular data modelling / workflows issues..

Very helpful indeed.

πŸ‡¬πŸ‡§United Kingdom alastairworters

So.. following your help and some further reading, I decided to use workflows (within core) with ECA to automatically update the workflow status, as certain milestones were met. However, I've now run into another issue, which looks like I will need to change my approach again, and I am hoping you could possibly let me know your thoughts on the best way forward using ECA to 'automatically' update the state of a workflow...

As per my initial comment (#1), I am looking to build a way to follow the progress of a specific job allocated to a contractor, changing the 'status' of the job as certain milestones are met throughout the task. And with your guidance, I have been able to get the 'status' automatically updated using ECA, along with ECA Workflow module, working with the Drupal Workflows (core) module..

Unfortunately, although this solution has been testing well today issuing a single job to a contractor, I cannot find a way of introducing multiple jobs being issued to various contractors within the same project, and can only get it to control the workflow of a single 'job' within a main 'project' content type.

e.g. A new Project (a content type) is created by a user that, based on the answers given, automatically sends emails to various contractors, instructing each of them to carry out a specific job, all as part of the main project. Then the plan is to allow each of the contractor's progress to be tracked through the various workflow states, from the initial 'Instruction' through to their specific job within the project being automatically marked as 'Completed' when the last milestone has been reached.

Now, after introducing more than one job with the project, I see that only one workflow (made within the workflows core module) can be applied to a content type... meaning that I can only control the status of one 'job', with in the 'project' content type...

Anyway, after a bit of reading this evening, it appears that the Workflow (contrib) module allows multiple workflows to be applied to a content type.

Hopefully that all makes sense....??

So my question is this - Please can you let me know how ECA interacts with the Workflow (contrib) module.. ie. is there a elegant task/action I can use within an ECA model that allows me to change the state of a Workflow (contrib) based workflow, just like the ENTITY WORKFLOW WORK STATUS: TRANSITION one that works with the Workflow (core) workflows..?

As always, I have exhausted my caffeine allowance and my skill levels are letting me down..

Thank you...

πŸ‡¬πŸ‡§United Kingdom alastairworters

Thank you again Jurgen.. Very helpful and I now have the model working!

One last question on this, if that's ok.. and not really specifically on ECA. But maybe you would be kind enough to tell me what would be the token to use, for displaying a message to the user after the transition has happened, saying "The Workflow Status has been updated to: [work_status - New Status]" ?

Thank you...

πŸ‡¬πŸ‡§United Kingdom alastairworters

Hello again,

I have changed the process to work with the workflow module, but again am struggling to get an ECA model to change a field value from one state to another..

Are there any instructions, or even video tutorials, on how to move from one workflow state to another using ECA?

Thank you and apologies for not being able to figure this out on my own.

πŸ‡¬πŸ‡§United Kingdom alastairworters

Thank you, for both the ECA solution and also the suggestion for the alternative way of solving the concept… with Workflow or State Machine.

Sometimes I should take a step back from the problem and look at the bigger picture, rather than heading down a one way path!!

Thanks again 😊

Production build 0.69.0 2024