New post
AllAccepted answers
Eduard Lebedyuk · Mar 13, 2018

I'm calling load code like this:

csession ensemble "##class(isc.git.GitLab).load()"

ObjectScript:

/// Do a full load
/// do ##class(isc.git.GitLab).load()
ClassMethod load()
{
    try {
        set dir = "/src"
        do ..log("Importing dir " _ dir)
        do $system.OBJ.ImportDir(dir, "*.xml", "c", .errors, 1)
        throw:$get(errors,0)'=0 ##class(%Exception.General).%New("Load & compile error")
        halt
    } catch ex {
        write !,$System.Status.GetErrorText(ex.AsStatus()),!
        do $system.Process.Terminate(, 1)
    }
}

This way process terminates abnormally on error:

do $system.Process.Terminate(, 1)

And it's usually reported as error in CI/CD systems.

Additionally you can grep for "Load & compile error".

I'm currently writing a series of articles on continuous delivery, check it out (latest part).

Eduard Lebedyuk · Mar 12, 2018

What version of Cache does it require to work?

If think it requires 2016.1 but 2016.2+ would be preferable.

I notice in the readme that it says to create a / web application. Did you literally mean "/"?

You can create non-root (/something) web application, that should not be an issue on windows clients iirc.

Read-only office documents

Are OPTIONS requests processed correctly? Check OnHandleOptionsRequest method - you'll need to write a method that processes all OPTION requests and returns relevant headers.

If the problem with read-only Word files persists, it can be fixed by one of the above:

Additionally I recommend:

  • Installing 2017.2 (anything 2016.2+) separately and checking that it does work
  • Installing Wireshark and capturing a sample exchange on 2014.1 and 2017.2
  • Compare these two sessions to understand what fails on 2014.1
Eduard Lebedyuk · Mar 9, 2018

Can I still add code in Business Studio and it maintain integrity to be able to still open in the BPL editor?

It's easier to use one tool to modify BPL.  <assign> is available in UI so you can add it without writing XML at all.

  then the BPL hung.

I tested that behavior in BS only and it works there fine there.  Maybe it causes BP to break. You can try to set SessionId just before sending request to other BP or BO and then reinstating old SesionId  value back. That way persistent  session value on disc would stay the same and BP can maybe survive unload from memory.

My recommendation is to iterate over result set in BS rather than BP, then send each new snapshot (preferably preprocessed  in BS) to BP with new session for each object.

Eduard Lebedyuk · Mar 9, 2018

I want to know if it's possible that when I selected a date in one widjet affected also the other widjet with the same date. '

Yes. When you specifying the target for the widget control you can specify:

  • Empty string for current widget
  • * for all widgets
  • Widget name for some specific widget
  • Comma-separated string of widget names - to specify arbitrary number of widgets

Fourth case sounds like what you need.

If exists the possibility to create a generic date and when the user choose the range of date, will affect all of the widjets, independent that are different dates.

Can you elaborate on that? Do you mean filtering by week/month/season/year/etc.? That's possible.  There are a lot of ranges available, but you can add your own by extending %DeepSee.Time.AbstractLevel.

Eduard Lebedyuk · Mar 5, 2018

For password authenticated web applications it is possible by following these steps:

  1. All brokers effectively have Parameter UseSession = 1;
  2. REST web application and client web application allow only authenticated (i.e. password) access.
  3. REST web application and client web application have reasonable Session timeout (i.e. 900, 3600).
  4. REST web application and client web application have the same GroupById value.
  5. REST web application and client web application have the same cookie path.

If all these conditions are met, user would only consume one license slot per session and perform only one login.

Check out my upcoming webinar, we definitely would be discussing authentication.