using the details provided from the above link you will set up the following
64k field=Information 4k field = Update
Everytime the call is saved any information will be appended to the persons name and time and formatted with a carraige return and ll this will then be appended to the 64k field. When the call is opened the 4k field will be cleared so that new updated can be entered and appended to what ever exists in the 64k field. This creates the log with time stamps and details of the person who did the update.
It will do what you are looking for saving the need to look at history lines to se up dates
Thanks I've sort of got it tork. How do you get it to clear the information field after it has updated information history and how do you get it to space out the updates so they are not bunched together
Q1- use a UI rule to make empty the update field when the call is opened. Try a UI rule rather than a DB rule so that if the DB rule is slow firing the update is not removed too soon
Q2- in the document on the link to the other thread you will see that there are a number of concatenations. You need to concatenate the registration modified name with the space that will appear between the name and the date then another concatenation to add a carraige return that will then have a final concatenation to add the update.
Use the fixed attribute in the rule to add the spaces and carraige returns.
Read through the other link again and see how the concatenations are set up.
I just got back into a test lab I have for Ver 5 (no SP's) and guess what. I cannot enter a fixed value for a carraige return and libe seperator variable will work as you have experiences (i.e. will print line seperator to the text field).
Options - try SP1 or SP 2 wjich has just been released or askk HP to confirm if thsi works in either SP.
Or create a custom text field. Use a template to set it to a value of a carraige return when you opena call. Then concatenate this "attribute" (not fixed value) to the rest of your DB rule. I hope the carraige return behaves as it should in the templates
I tried this last night trying to use the template to add a carraige return to a text field and then using this in a rule to post back - and you guessed it - it doesn't allow me to do that. It won't save a carraige return. You could ask hp if this is resolved in a hotfix or SP 1 / SP2.