Pesquisar

記事
· 2024年7月19日 3m read

Celebrating a Champion of Our Developer Community

#開発者コミュニティ公式

Among the numerous authors present on the InterSystems Developer Community, there are unsung heroes who leave a lasting impact through their dedication and contributions. One such member is @Ben Spead, whose experiences and milestones have greatly shaped our Developer Community. He has consistently championed the communities, starting with Zen Community in 2008 to being an early participant in the Developer Community's beta phase in 2015.

🤩 Let's take a closer look at Ben's journey with InterSystems technology and our Developer Community...


Ben began working for InterSystems as an intern in June 2003. His enthusiastic involvement in the beta phase available to InterSystems employees marked his entry into the Developer Community in 2015. Over the years, he has witnessed the evolution of InterSystems products and the Developer Community. Here is what he says:

  • Launching the Zen Community gave me a real first-hand view into the value in creating transparent technical discussion around our products in a forum that benefits employees, customers and prospects
  • Building the Application Services Department within InterSystems has helped me to learn how to build on the personal skills and passions of members of my team in such a way that our users benefit and those under my care can flourish and grow
  • Architecting our global change control tooling for implementation and internal application development has convinced me of the value of focusing on simple (but not simplistic) reusable processes which helps to break down silos between different teams
  • Leading our initial Cloud Deployment initiative for FHIR Transformation Services with AWS underscored both the flexibility of our data platform as well as the brilliance of the InterSystems employees, the combination of which makes it possible to tackle extremely challenging new projects with excellence!!  

One notable challenge he tackled is the 'last mile problem'—ensuring users are aware of new features and enhancements. By implementing a centralized internal newsletter, he created a reliable resource for developers, reinforcing the importance of a centralized learning platform, much like our Developer Community.

Since joining the Developer Community, he has witnessed tremendous growth in membership and content quality. As a manager of a development team, he encourages all developers within AppServices to actively participate in the Community. This involvement benefits both his team and the broader community, creating a win-win scenario where many can benefit from shared experiences and knowledge. He also plays a key role in reporting bugs and suggesting enhancements, helping the platform evolve continuously.

Ben's journey has been punctuated by rewarding moments - including this interview recognizing his contribution to the D.C!  His advice to newcomers is to ask questions openly and engage with others' queries, fostering a culture of continuous learning and mutual support. His personal passions include spending time with his family, his faith, and tackling DIY projects, continuously applying his problem-solving skills outside of computer science. 

Looking ahead, Ben aims to enhance his team's engagement in the Developer Community and drive meaningful conversations among global users of the CCR application.  

We are immensely grateful for Ben's unwavering dedication and significant contributions to the Developer Community. His journey and achievements inspire us all, exemplifying the true spirit of collaboration and growth. Here's to Ben — a true champion of the Developer Community, whose journey inspires us all to strive for more and embrace the future with innovations and collaboration.

👏 Let's all congratulate Ben and thank him for his contributions to InterSystems and our Developer Community! 

14 Comments
ディスカッション (14)7
続けるにはログインするか新規登録を行ってください
質問
· 2024年7月19日

How to make a custom studio document work correctly with $System.OBJ.Load() ?

#InterSystems IRIS #VSCode

Hi all,

I have some .vm (Velocity Templating Language) files that I'd like to be able to load into IRIS with the $System.OBJ.Load(filename) command, but it seems that only accepts XML files.

I've tried adding import/export logic in my custom studio document that will wrap the velocity content inside an XML document and vice versa, I've changed the existing Velocity files to have the extension .xml and be wrapped in XML, and I've included a .dtd file for them to reference. However, this doesn't seem to work.

Does anyone have suggestions for how can I make my custom studio document work correctly with $System.OBJ.Load()?

4 Comments
ディスカッション (4)2
続けるにはログインするか新規登録を行ってください
お知らせ
· 2024年7月19日

[Vidéo] Renforcer la coordination Ville-Hôpital et la consolidation de services numériques

#ビデオ #HealthShare

Salut la Communauté!

Profitez de regarder la nouvelle vidéo sur la chaîne Youtube d'InterSystems France :

📺 Renforcer la coordination Ville-Hôpital et la consolidation de services numériques

🗣 Intervenant : @Florence Cureau, Solution Architect InterSystems

Entre la crise de l'hôpital et un patient qui veut être acteur de son parcours de santé, une révolution est en marche. Florence présente HealthShare, qui apporte une réponse rapide et éclairée, en reliant le monde de la médecine libérale et l'hôpital pour une prise en charge globale. Découvrez comment HealthShare vise à créer un cercle vertueux au bénéfice du patient.

Abonnez-vous à notre chaîne youtube pour plus de vidéos et restez à l'écoute !

1 Comment
ディスカッション (1)2
続けるにはログインするか新規登録を行ってください
記事
· 2024年7月18日 2m read

InterSystems 常见问题系列--如何使用命令获得应用错误 (^ERRORS)

#ヒントとコツ #Caché #Ensemble #HealthShare #InterSystems IRIS #InterSystems IRIS for Health

InterSystems 常见问题系列

使用 ErrorList 查询 SYS.ApplicationError 类.

  • 注 1: 在 %SYS 命名空间中运行.
  • 注 2: 这是个非存储的utility, 所以我们用 %ResultSet 类而不用 %SQL.Statement.

执行命令的例子如下.

USER>set $namespace="%SYS"   //equal to zn "%SYS"
%SYS>set rset=##class(%ResultSet).%New()

%SYS>set rset.ClassName="SYS.ApplicationError"
%SYS>set rset.QueryName="ErrorList"
// The first argument of the query is the namespace name, the second argument is the date (in MM/DD/YYYY format).
%SYS>do rset.Execute("USER","08/17/2020")

// To display the results on the screen, execute the %Display() method.
%SYS>do rset.%Display()
Error # Error message   Time    Process DisplayPID      Username        Code line
1 <DIVIDE> 02:43:10 2536 2536 irisowner

1 Rows(s) Affected

%SYS>do rset.Close()

以下显示如何获得在浏览行时获取SELECT的列值The following shows how to get column values ​​of a SELECT while navigating through rows.

使用Next()方法来移动到一行（如果行存在的话返回1）

获取一列的话使用 Get("column name"). 具体列名，请参考类文档里面的ErrorList 查询描述。

关于ErrorList 查询的列名.

%SYS>do rset.Execute("USER","08/17/2020")

%SYS>while rset.Next() { write rset.Get("Error #"),"-",rset.Get("Error message"),"-",rset.Get("Time"),"-",rset.Get("Code line"),!}
1-<DIVIDE>-02:43:10-

For terminal viewing, you can also use the ^%ER routine.

Execute the following while in the namespace you want to reference (the example is executed in the USER namespace).

The green bold underlined text indicates the input area.

USER>do ^%ER
 
For Date: ?L
Thu 09/17/2020  (T)   2 Errors
Mon 09/07/2020  (T-10) 3 Errors
Mon 08/31/2020  (T-17) 1 Error
Mon 08/24/2020  (T-24) 1 Error

For Date: 09/17/2020  17 Sep 2020   2 Errors

Error: ?L
 1. " *a"  at  9:05 am.   $I=|TRM|:|13484   ($X=0  $Y=15)
     $J=13484  $ZA=0   $ZB=$c(13)   $ZS=262144 ($S=268271680) 
 2. "^%ETN"  at  9:05 am.   $I=|TRM|:|13484   ($X=0  $Y=17)
     $J=13484  $ZA=0   $ZB=$c(13)   $ZS=262144 ($S=268263368)
     %ETN     ;%STACK-related error log

 Error: 1
 1. " *a"  at  9:05 am.   $I=|TRM|:|13484   ($X=0  $Y=15)
     $J=13484  $ZA=0   $ZB=$c(13)   $ZS=262144 ($S=268271680)
Variable:

Error:
 
For Date:
USER>

日期: 错误发生的日期格式为 mm/dd/yyyy

错误: 明确错误编号.

看完之后，回车即可退出。

ディスカッション (0)0
続けるにはログインするか新規登録を行ってください
記事
· 2024年7月18日 1m read

InterSystems 常见问题系列--如何在global ^ERRORS 里面加入应用日志

#ObjectScript #ヒントとコツ #Caché #Ensemble #InterSystems IRIS #InterSystems IRIS for Health

InterSystems 常见问题系列

可以通过 TRY-CATCH 来完成:

 #dim ex As %Exception.AbstractException
 TRY {
    //Code that causes an error
  }
  CATCH ex {
     do ex.Log()
  }

如果用了 ^%ETN, 从BACK 接入点 (BACK^%ETN)处调用.

请参考另外一篇文章: 如何使用命令获得应用错误 (^ERRORS)

ディスカッション (0)0
続けるにはログインするか新規登録を行ってください