How to combine Views, Rules and EVA to record submission? I have a Drupal 7 site and I'm using Views, Rules and EVA.

I have a specific requirement that I am sure can be achieved with the modules, but I am having no joy configuring a working process.

I have an 'Application' content type, which has a submission form embedded (i.e. visitor completes submission form for the role they are applying for).

As all visitors login in order to submit an application, I would like to record each application they make into a 'My Applications' view/block, within their User (/user) page.

I see the process as something along the lines of:


Visitor completes application form and clicks a Submit button.
Via Rules, an association/reference between the user and the specific role/application is recorded.
Using EVA, a custom view will list the applications the user has made (showing only his/her applications, unless admin).


The part I am failing with is how to configure a Rule, triggered by the submit button, that links the user to the specific application, in such a way that it can then form the EVA view.

Has anybody implemented a similar process? Recording applications (for jobs, events, meetings etc) and allowing users to see those they have applied for must be possible?

I would be happy to use an entirely different approach if there is a better method vs. the  Views/Rules/EVA idea.

Suggestions gratefully received. Thank you.
I am not familiar with EVA but it looks pretty good.

I have a similar use case with entityform.

You can embed entityforms on nodes using the entityreference field.

Now entityform comes with a view already set up that displays a user's latest entityforms. 

Here is a screencap of the view configuration - it displays a user's latest form submission(s).



You can then add a 'block' version of this view (the 'add' button in the top left corner.)

You can then configure your new block to only show up on the logged-in-user's /user page. 



Hope that helps. Incidentally let me know if you are trying to get the form-fields to be pre-populated with user details. 

Based on your comments: