Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store user and edit type in Actionkit templatehistory table #4

Open
ejucovy opened this issue May 11, 2013 · 0 comments
Open

Store user and edit type in Actionkit templatehistory table #4

ejucovy opened this issue May 11, 2013 · 0 comments

Comments

@ejucovy
Copy link
Member

ejucovy commented May 11, 2013

Right now, when you edit an Actionkit template through the system (either directly or using the checkin/deployment feature) the Actionkit templatehistory table ends up with null values for "username" and "edit_type".

It would be better if the logged-in user's username ended up in there, and maybe an edit_type of "api", or even "akcode_direct_edit" vs "akcode_checkin".

This may involve filing a feature request with WAWD -- I can't figure out a way to do this using the API currently. Ideally, the API method for saving a template would let you provide username and edit_type directly.

(The workaround would be to save the change to the template, then look up the new templatehistory object that was just created, and then make another API call to put username and edit_type attributes on that object. This involves at least three remote calls though, and it also is hard to do -- that lookup for the latest templatehistory object doesn't seem to work, because the REST API doesn't let you list the most recent templatehistory object(s) for a given template, and the client-db connection doesn't seem to be receiving the new templatehistory object quickly enough to do this right after the save. So to implement this without a new AK feature, it seems like we'd need to use asynchronous jobs to poll for templatehistory objects and set their values when they show up.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant