My point is we have one field called "Information" on service call form. Engineers update this field whenever there is any change in service call.
Whenever this field gets changed, it gets shown in history page as areauditing this field. But when we double click to see entire information in 'History line form", it shows trancated information but in "Subject field" instead of information field.
Basically that is the way auditing works - the subject field in the history shows the old and new values of the field. The Information field in the history is just for you to add other comments if you want - it is not used when a system history line is added.
What Mark was describing was an alternative way of approaching this. If you would like more assiatnce on this just ask,
Many clients using HPSD use a "diary" style system.
To do this you activate the 64Kb text field (say call it User history) and have a 4K text field that will act as the source for diary updates; this can be the OOTB Information field or a custom 4k text field (say call it user log).
Then you set up DB rules that are something like: When SC is created, when user log is not empty, action: update data to use the concatenate function to combine the current source entry with the entries already in the user history and a timestamp + name of user who made the change. For example when using the Information field as the source:
When service call is created where NOT (Information (*) is empty) Concatenate Inf into inf history (Update Data) Information History set to (Concatenate (Concatenate [Registration Created by Display name] With (Concatenate , With (Concatenate [Registration Created] ))) With (Concatenate [Information] With (Concatenate
With [Information History])))
You would need a similar one for modified and we ususally also have a rule which empties the source field.
Hope this helps, Ruth
(and it does it might be good to assign points - I see your profile says you have assigned points to 0 of 50 responses to your questions!)