ExactOnline for coreBOS

[Guido1982]

Quote:joebordes wrote:

Not necessarily but it is a good and clean way to proceed. You can have a "tools" file and put them in there also.

Right now I'm thinking about moving all my classes to a subfolder of the module folder, would that be in line with the application structure?

Quote:joebordes wrote:

If you don't want to explicitly expose the tests to the users you can leave them in the test file. In fact you can leave them there even if you do expose the results to the user.

I'm also not wuite sure about what the index.php file does. I know it loads when no further action is specified on the url, but I have to study some simple modules further I think.

Quote:joebordes wrote:

I don't think the Settings functionality is documented anywhere. It is rather simple: you define a few entries in an array that indicate the icon, title description and file to execute. coreBOS will add the "hammer" settings icon and paint the box for you. When the admin user clicks on the link he will be redirected to the link you indicated, from there on it is all yours, do whatever you need to do.


Start by looking at the existing code. For example I uploaded yesterday our Confidential Information module that has two custom Settings sections:

https://github.com/tsolucio/Confidential-Information/blob/master/modules/ConfidentialInfo/Settings.php#L69

Thanks, I'll look into this.

============================ MAYBE ===========================
I have some more functionality in mind for which I'd like to use the standard 'record keeping' functionality of coreBOS. Because I want to automate every action through workflow tasks, I was thinking maybe it would be a good idea to create some method that updates the 'normal' table (and move the Settings to a different table) with a record each time. This mainly to create a detailed track about what was sent to Exact and if any errors occured. I'll take a look at the default functionality of a skeleton module and see how I can incorporate this behaviour. Keep in mind these will be 'view only' records, only to keep track of what the module is doing. Tomorrow I will start studying existing modules.