Differences

This shows you the differences between two versions of the page.

--- pracro:post-commit-hook [2011/12/02 10:16] – deva
+++ pracro:post-commit-hook [2011/12/02 10:42] – deva
@@ Line 1: / Line 1: @@
 ======Post-Commit-Hook design======
 A method for running a script on session data is needed on session-commit (possibly also discard?) in order to for example be able to post data to external databases when the data are commit to the pracro database.
-The mechanism should be designed so that it is also able to handle journal commits and thereby replacing the existing ''<resume>'' tag:
+The post-commit-hook scripts are to be executed //after// the commit has been performed successfully to the database.
+The mechanism should be designed so that it is also able to handle journal commits to pcpraxis (currently handled in c++ via upload server) and thereby replacing part of the functionality in the existing ''<resume>'' tag:
 <code xml>
 <?xml version='1.0' encoding='UTF-8'?>
@@ Line 18: / Line 20: @@
 What should be available to the scripts on run-time?
 All committed values from all template macros. Each macro should have the values stored separately so that overlapping names do not overshadow each others values.
+All generated resume texts must equally be available in order for the script to be able to commit data to the pcpraxis journal.
+The data can therefore be made available in a preloaded map hierarchy of macros/names/value in the following manner:
+<code>
+value = vars['macro1']['name']
+</code>
+All resume texts are stored with the '''resume''' name making it possible iterate the macros and producing the complete journal text by simple concatenation.
+An important feature of this list is that the native order of the macros are the same as in the template - **NOT** sorted alphabetically or similar!.
 =====Script placement=====