you are not quite correct:
abstract class %CSP.Stream is a base class for
you decide which one to use
Where is the problem ?
First bid:
#1) Subscript > 511 chars is not allowed.png)
#2) your browser broke the CSPCHD token for some CSP page
.png)
Thanks @Bob Kuszewski !
Sniffing through System Globals and Journals I found ^oddPYTHON and more:
I'm convinced it works as before
Thanks @Bob Kuszewski !
Sniffing through System Globals and Journals I found ^oddPYTHON and more:
I'm convinced it works as before
contact ISC sales, buy an appropriate license, and you get access to WRC and the Kit repo
Last version of Caché was 2018
I see. just Sub-sessions:
If this is your own CSP page you may set %session.EndSession =1
.png)
OR
you have a dummy page that does just this and you call it manually
I did it mostly during testing
check Network Coding and Character Coding (Sorry example just in German)
.png)
Check available disk space
since the invention of Grace Period by BdK I'm fighting hanging CSP connections.
my approach:
.png)
.png)
in most cases, it is sufficient to get free locked licenses
Robert
YEAH! Coffee in Belgium was always great for me
when I worked in Italy and Spain 40+ years back we always went to the cafeteria next door.
They served excellent "café correto".
BTW: I'd definetly prefer Sangia over Cold Water
😋
I assume "water cooler tank" has the same social functionality
as the kitchenette with the common coffee machine in central and northern Europe
Hi @Raj Singh, @Lorenzo Scalese , @Evgeny Shvarov
.png)
I suggest to have globals and routines in separate databases.
Keep the routines always local and only use Global DB over ECP for shared access.
The price is you have routines to maintain in 2 instances.
Thank you for the motivation!
Thanks.
This matches my experience. Issues require explicit Close to vanish from main-page counter.
did you use SQL from SqlShell?
like this?
USER> Do $system.SQL.Shell()
......
SQL>>SELECT .....
So I assume an id of 1 will suffice. WRONG
^DocM.DocumentImageD(1,1) =
indicates that the id is "1||1"
therefore after
AVCWS>Set obj = ##CLASS(DocM.DocumentImage).%OpenId(1)
write obj shows it is NOT and <OREF>
and obj.ID fails as a consequence:
But this is all visible in the class definition of
DocM.DocumentImage.cls
Looks like old cached queries don't know new index ???
try drop cached queries from SMP
Add it to the GitHub package in any case. with a short notice in README.
I have no experience with using ZPM outside IRIS.
OK this is fixed and works fine.
Some hints from personal experience
Sorry, there is a bug:
from config.py:
# Default config variables
import json
import os
import sys
import base64
APP_PATH = os.path.dirname(os.path.abspath(__file__))
JSON_CONFIG_PATH = APP_PATH+"/config.b64"
.....BUT it is missing in your repo:
irisowner@2bbb2b066320:~/dev$ irispython ./rh/flask/main.py
/home/irisowner/dev/rh/flask/app/config.b64 not found
Ooops !
No discussion: Business Operation and Outbound adapter is a combination you should not break .png)
But to trigger a second Business OP You just need a Business Service that you kick,
no need for a Busines Process in between. Old ENSDEMO shows such examples.
eg. DemoRecodMapper.png)
Here the FileService is the driving part.
another example uses a service that triggers itself DemoDashboard.png)
It just lives on his timeout setting
Here it has nothing to do then updating some properties
But it could be anything. eg Kicking another Business Operation
OBJECTSCRIPT:
forx=1,3,4,5 {
; ///some code
}
Translation from the French community posted by @Lorenzo Scalese
----------------------------------------------------------------------------------------------------------------
Hi,
ISC should keep a copy of the original repo until a new release on OEX (this is eventually the case already)
If a package gets orphaned, it seems to be complicated to hand it over to another member of the community if this copy doesn't exist.
The account on GitHub could have been closed or the repo could have been deleted. This complicates the situation. We could. of course, try to recover the content from ZPM. But this could be wuite a huge effort of re-engineering. [ If it is available in ZPM at all. -rcc]
Regarding the deletion of the package.
I'm not against the idea, IF there is a valid reason.
It happened to me that I deleted a package because a new functionality of IRIS made it obsolete.
Anyhow, I left the repo on GitHub public in order not to lose the contained knowledge.
In that case, we could decide on an option to "archive" the package
Not everybody works with the latest version of IRIS. So this might be interesting in some cases.
----------------------------------------------------------------------------------------------------------------
Thank you & Merci @Lorenzo Scalese
Just to complete the case mailing was step 0 way back
I received no reply and canceled the related PR which was out of data after 3+ months