Active Agenda Community

[zsimre]

Hi Dan

may I ask you to give me a practical example how to use Documentation module ?
I registered a document in this module, assigned it to some specific situation (BaselII script loaded, thank you for this to you), than registered an incident in ire, assigned one of above situations to this incident - and tried to add document with "document" link from right panel, but no document came up, I can just fill some fields (date, status, details), but read-only fields are empty and no way to change them in edit panel.

[danzahlis]

Hi Zsolt,

You've encountered another module awaiting our "module walk-through." We simply need another coder that can sit with me and conduct the walk-through to complete/refine functionality. I have exhausted the XML capabilities and need a few custom "tweaks" to complete a number of modules. Until we can locate someone interested in providing some code assistance, these issues will have to wait until Mattias can free himself.

Once he returns from Australia, we plan to sit down and review a logical division of code/labor so that we can actively recruit a person to assist with these tasks. We will try to find someone locally AND via sourceforge.

One of our top priorities will be the Incident Reporting and related modules since many people seem to have migrated to them first. We will talk about completing these tasks before securing more assistance as the priority for the domain is rapidly outrunning the "pure tech."

Mattias just spent a week sitting with a group of manufacturing ops people and I know they focused heavily on the same modules during their discussions. We will keep you posted. Sorry for the inconvenience...Dan

[zsimre]

Hi Mattias,

I think Documents module has a small bug, because it is simple does not work. There is no way to fill Document form, and later use this document in Incident Reporting module - the earlier registered documents are not visible any way in ire module.
Pls help, we need to register some documents as incident activity "forms" as soon as possible.
br
Zsolt

[mattias]

Hi Zsolt,

The Documentation Screen in Incident Reporting should display relevant required documents, depending on what situation(s) occurred.

What you are seeing is not exactly a bug but missing functionality. This is one of the really important things to complete, but I'm also really busy with other important tasks. Sorry that I can't give a time line other than "soon"...

Mattias

[zsimre]

hi Mattias,
thank you, i'm waiting for your development.
sometimes I think there are some modifications (may be this one also) which I can solve myself - may be it can be a help to you.
do you have any system documentatoion, coding requirements document or some like these to help "external" coders ?
br
zsolt

[mattias]

Hi Zsolt,

You are more than welcome to submit fixes and new developments to us. If you see something you think you can fix, please do send it over.

I believe TortoiseSVN can even make "diffs", but otherwise I'll be just as happy with whole files.

The Documentation-by-Situations functionality in Incident Reporting is probably one of the more challenging projects to take on as a beginner. What is challenging is that the list will need to display rows that are simply the product of joining applicable situations with their documentation requirements (not actual records until they have been saved). It's a situation that is somewhat similar to Shared Expectations in Partnerships.

In general, there is developer documentation in our Wiki, as well as in the source code itself. I know it is not complete but I am more than willing to answer any questions you may have.

Coding standards: I try to follow the PEAR coding standards where applicable, but there is still some older code that doesn't follow this.

My notes on debugging might also be helpful to coders.

Cheers,

Mattias

[zsimre]

Mattias,

i made a short check on this topic, and I think it can be solved on xml-specification level, because no neeed to touch the code itself to define module depencies - and the content of document module's grid in other modules depend on depencies - I think.
Is that correct or not ?

[danzahlis]

Hi Zsolt,

The planned design of the Documentation module requires coding beyond the XML specification. However, it sounds like you may be looking for functionality that can be achieved with the XML. If this is so, we can do this for you rather quickly.

What precisely would you like to achieve?

The current plan is to automatically populate the Documentation edit grid, within the Incident Reporting module, based on documentation recipient requirements established within the Documentation module. These rules/assignments are stipulated on the Situations and Recipients screens within the Documentation module. This requires some custom coding to accomplish.

If you just want to display the documentation associated with the incident reporting module (irrespective of situation), that can be done quite easily, just let us know.

Thanks...Dan

[zsimre]

your original plan is more better and rational than the simple situation-independent solution, therefore I vote for original plan.
but my knowledge now is not enough (yet...I hope) to solve it, I need some weeks to read the module-generator scripts to understand how the logical architecture is built up in .gen files.

br
zsolt

[mattias]

Hi Zsolt,

Thanks for studying my code, I really appreciate it. In this case, there is some custom programming, not just XML changes, required in order to get the intended functionality. Or, to put it another way: I need to expand the XML vocabulary to handle what we want this to do.

Cheers,

Mattias

[danzahlis]

Hello all,

We have posted some changes to the Documentation module over the weekend. To enable tracking requirements of a quality system, we have added the following sub-modules/capabilities:

Document Distribution: Tracks the physical distribution of controlled documents.
Document Transactions: Tracks the Deposits, Retrievals, and Destruction of documents at each physical location.
Document Requests: Tracks requests for the creation of a new document and/or the modification of an existing document.

We're still working on the "ties" between documents and other modules throughout the application (e.g. who needs to receive a copy each time a record is entered into a specific module).

Stay tuned...

[danzahlis]

Hello All,

The latest SVN addresses the "hooks" between Documentation and Incident reporting.

Documentation module:
* Associate situations with a document
* Associate recipients with a document

Incident Reporting module:
* Enter an incident and assign the respective situation/s
* "Documentation" screen. A grid will appear listing all documents and recipients required.
* Use the "Quick Edit" icon within the grid to record and save documentation sending details (e.g. Date/time, method, status).

This results in a list of all documentation status' related to all incidents. In other words, "Have we sent documentation to everyone that requires it or not?"

We will now work on similar functionality between Incident Reporting and Contacts ("Did we notify everyone?")

...and then - auto-population of situation response steps, by role, by person assigned.

Please play with this new functionality and let us know your thoughts...Dan