November 14, 2019
  • 1:52 pm Hong Kong protests: university becomes battleground between protesters, police
  • 1:52 pm How to Feed a Baby Parrot with Healthy Diet
  • 1:52 pm What Happens At A Divorce Trial Setting Conference
  • 12:51 pm 3 Earnings Option Strategies
  • 12:51 pm KING 5 aviation specialist on Boeing earnings report

– [Mark] Good morning everyone. This is Mark O’Brien. I’m a Director at CM
First and I’m really happy to be hosting today’s
CA Community Webcast. Thank you very much to the CA Community for agreeing to host today’s webinar. We have several speakers lined up for you. First I’m going to transition over to Steve Salomon, who is
the CA Product Management main person for CA 2E and CA Plex, and then we’ll follow up with a couple of lightning technical talks, which are very popular with the community. It’ll be Roger Griffith of Eaglesun and then Pradeep of CM First Group will be talking about that. If you’d like to share your expertise with a CA product, such as Plex or 2E, we do have a, kind of a bounty program for you and I’ll let Steve go into that a little bit more and then talk to us about what’s happening with
our community worldwide. Take it over Steve. – [Steve] Thank you, and it’s (speaks foreign language) to our folks we want to say hello from Argentina and
Italy, welcome, welcome. (speaks foreign language) Steve Salomon. (speaks foreign language). I am the Product Manager
for CA Plex and 2E. I love doing these little
conversations with you guys and today we have a great session. The Lightening Talk is
hey, where are we at, what’s CA working on, and great tips by you guys, the customers, and Roger
has stepped up to do one and he’s gonna show you
some of his favorite stuff, and then Pradeep is going to join. and then the whole thing
is where are we at, and tips to
make you more successful. If you have great tips,
that’s where we want you to raise your hand
and do one of these. So after you listen to Roger
or Pradeep’s presentation I’m sure you’re all gonna
say, I have a great tip everyone else should know and we want you to be on the next one. So, we schedule these
every couple of months. Drop a not to either Mark or myself, Ben, your community
leaders and we will put you on the agenda. The more we help each other,
the more we will all beneft. So for my portion of
today’s Lightening Talk, let me do a quick The Road Ahead. So I tried to do, kind of, where we’re at and what we’re working on
because I’m talking about futures I always have to put in
the legal disclaimer, before you make a financial
decision from anything that you hear in today’s
meeting please reach out to us and let us give you
their most recent information. We regarding an Agile shop, we change our road map constantly to try to react to your needs as customers. One of the big things
that I want to remind everybody out there if
you are a Plex customer the 7.2.1 roll up Cumulative
PTF known as PTF002, we put in our name, has
a lot of updated PTF. Over the past year, year
1/2, we worked really hard on the Plex, working with all
of our customers out there on your issues that you reported,
creating fixes for those putting them out in PTF001
and then a roll up in PTF002. I mean there are a lot of fixes out there. There’s probably more than
50 between the combined. You will have a much better experience once you get to 7.2.1 PTF. Don’t forget there’s also
some performance enhancement so if you are suffering from
group model extract update it’s taking a long time, be sure you try to get upgraded to this one because you’ll get some speed performance out of that. Just a reminder, once
you get there you’ll have a smoother, better environment for your development organization. Here’s the big change coming
from product management originally we had announced
that CA Plex 7.1 and 7.2 were going to go to end their
service in December of 2018, along with CA 2E release 8.6. Then, I got feedback from the customers and from the advisory board
that by the way if we send out end of service announcements
in December they get lost. People are out on vacation,
you get all of these emails, you don’t have time to deal with it anyway in the end of the year rush. We said, okay, what we’re gonna do is we will send them out in January. So that has moved the date. End of service, end of
support for these products is now scheduled for January 31, 2019. So if your management
has concerns about that, you’d like to meet with either
the principle architects from one of thee products
from our services and support or myself to talk about what
you need to do to upgrade, we have services to help
you get there, absolutely. Now is the time you start doing that, start making your plans in
the first quart of this year if you can, or the first 1/2 of this year so that you can upgrade in the second 1/2 of the year and get current. That would be major beneficial. We are here to help you,
but if your management is concerned about it, hey,
I’ll be happy to get on a call with them, go through the process, we have a lot of customers
that have already made the upgrade and we
have a lot of experience and a lot of confidence
that you will be successful. So key change, EOS, January 31, 2019. We had a customer that was
recently asking questions about an upgrade, and I
said hey since my architect gave me all of these tips why
not share them with the group. This is kind of important
because if you are C++ out of Plex yes you have
to rebuild your code, due to compiler upgrade. But if you’re C#, you
probably don’t have to. This is one of the key things that came up in a discussion with
customer saying okay well, we see C# having to rebuild
and retest our application which is very very huge,
it’s quite time-consuming and expensive that we’ve
does an internal dev here at CA and Arun’s our architect, that’s why it’s his upgrade tips, His team has done some validation and as far as we aware a
rebuild is not required from our point of view. Now, if you’re using custom controls or something unique in your environment then you’ll have to evaluate that. But please when you do your plan, try doing it without
rebuilding your application and make sure there’s there’s no issues. We do have quite a few tips
that are documented out there remember all of our questions
and new documentation is online and Google searchable
and we call it DocOps and there are some links to
the different DocOps pages to help you see what you need to do, at least from a Plex upgrade to 7.2.1. We are working on
customer cases and issues, as you guys call them. It seems like the more than we talk and the more customers we engage with the more requests we get for assistance in different areas with
upgrading your issues. That has kind of extended our timelines when we’re doing new development and it’s always a difficult decision when we’re working on
fixes do we try to put it into the next PTF roll up. We are working on the CA
2E 8.7 PTF roll up one. So, for the 2E customers
out that are on 8.7 we have a lot of PTFs that we’ve done and now we’ll put them all
together into one big roll up and we’re doing all the
automation and testing about those and as we’re
testing and validating that of course you guys are asking
for more changes and fixes. We’re trying to make that decision on when we’re going to cut those off. So, just a heads up on the 2E folks, that if you have a case in you
guys are a priority for us. Cases probably coming
in the next month or so we’re gonna have to make
a decision and focus on cutting off the the roll up of the PTF and finalizing it to
get that out the door. It’s always a difficult decision to say hey we need you to wait a couple of weeks until we can finalize this to
benefit all of the customers. But they’ll let we’re in
that depths of that process and that’s what were doing at CA. If you’ve been helping with us on some of the items and validating those we truly appreciate your
efforts get that out the door. The other thing is we
would like you to ask you in the Webex here, does
it look like some of the text is being taught. But if you could set aside some time in the last half of this year to help us do the validation on
the next release of 2E. So, back on the 8.8
there’s a lot of changes that are happening for database support, that’s really the theme,
and it’s really aimed at everybody that has very
large databases for 2E. We can only duplicate many
customer scenarios on our side this is a request from your engineering product management team,
if you could put some time in your schedule for the last
half of this calendar year to help us test and validate that would be a great way to help, appreciate it. I love this cartoon because it says can’t you see we’re
too busy fighting a war to trial your product,
and it’s the same thing that happens in a beta. It’s, basically, every time
we make the product better we make it that you could
go faster, have less issues. But we need your help to get there. It really is a joint effort
and we do appreciate it. Something to consider if you’re 2E user, you’re an experienced 2E developer, please keep this in mind
that in the last half of this year we’re
going to be reaching out and asking for help. I would like to turn it
over to a good friend of mine, Roger, go Boise
State and I will turn it over to you and we
will make you presenter and you can take it home. – [Roger] Thank you Steve. Today I’m going to be
talking about a new tool that we use here at
Eaglesun Systems Products to help us to build our
releases and to do it as efficiently as possible
and I’m going to talk about why we need a tool
and all the benefits that it offers us. I think that this is an
appropriate presentation after Steve just talked about
how the entire Plex community has to move to 7.2.1
which requires a complete gen and build of all
of your WINC functions. This is a tool I think
that’s very appropriate. We are already leveraging the tool getting immediate value from it
and I think that once you see the tool I think
you’re going to also see where it very well may
be something that will help you in your efforts to
upgrade your Plex applications from one version of Plex to another or simply to upgrade the applications as you make changes to the application. A little bit about me, again,
my name is Roger Griffith. I worked for Eaglesun Systems Products we’re based in Tulsa, Oklahoma. I work from home remotely I just happened to be at at Eaglesun in Tulsa this week having meetings and going through some development stuff
that we’re working on. my email address is there. I am the world’s leading
CA Plex Evangelist. No one’s more passionate
about Plex than I am. I’ve already made
arrangements that when I die on my headstone, it’s gonna say, World’s leading Plex evangelist. I’d like to say those arrangements
have already been made, you guys don’t have to worry about it. Some of the things I’ve
done over the years as a Plex developer. I have developed and published
several different tools and patterns with Plex. These are free tools
that have been published on the Plex wiki, so
if you go to that link it will take you to other links that you can get directly other free tools. One of them is this tool I built called a Plex Upgrade Wizard that
it builds a list for you that you can use to help kind of automate your gen builds from 7.1 to 7.2.1. It’s a tool we’re going to
talk a little bit about today and it kind of plays into this effort. I mentioned that I worked for
Eaglesun Systems Products, this is a company that
was started back in 1992 by Cindy Wright, this is
a family-owned business. They developed this system which is they call it the Tribal
Assistant System known as TAS. It was originally built in
Obsidian which is now Plex and it’s been an amazing
tool for the company because it allows us to
do a lot of development with a minimal amount of people. We’re a small company with
a very large footprint. The company has 15
employees that are spread between various roles of
development and support. We’ve got 65 plus tribes
that span the United States. I say plus because it’s constantly growing the company has been in
a constant mode of growth ever since they started
and every year we add new customers, new tribes, spread across those 65 plus tribes we
have roughly 2,400 users that use our application. I mentioned that it’s been in a constant, sustained growth mode,
we’re constantly adding new tribes and we’re growing,
we’re adding new modules to our portfolio for the existing tribes. There’s all kinds of
opportunities for the company as we move forward. The application that has been developed is entirely WINC everything is C++. The core of the
application was built Obase and this is mainly because of the fact that the company got started
back on Obsidian version two and the bulk of the
application was in place before Patterns got there. Patterns comes along and
most of the new development is all done in Patterns, but the core of the application, the vast majority of the application is Obase. That’s just kind of an
overview of the product. The task product that
we have that basically starts off as based on what we call the central information file
which is a tribal member and we have all these modules
that basically connect to it. And each tribe has
different modules depending on what their needs are. Some of our tribes have
just a few of our modules and some of our larger tribes they have a lot of our modules. Every tribe is different in terms of what they use from TAS and
what their needs are. What’s kind of interesting about Eaglesun is that we actually support
and offer multiple versions of our application. This is something that most shops don’t do because it’s too difficult for them to do. It’s difficult the development, it’s difficult to support it. But what Eaglesun has found
is that with a tool like Plex it accommodates for it very very well. We have our application
is all in one model but we have variations of the
application within the model. Potentially 65 different
variations of the application in the model and the way it works is every time we get a new
tribe we create a version within the model for their tribe. All of our modules are all
developed in Plex levels, then what we do is for
each tribe we connect the levels that they have to their version and that is what makes
those modules available in their release. The way it works is
that let me also mention that as we add new
modules they’re included in the base release and
they’re basically turned on or turned off as far as
whether they’re available based on data driven architecture. We’ve got kind of the
old way we’ve done it where everything is basically
a custom build for them and then we’ve got the new
way that we’re moving towards which is we just include
all of the modules and we activate them based
on a licensing model. OK, on the first slide you
probably saw Clint Eastwood and here’s where that
plays into my presentation. We’re going to talk about
it there’s our buddy Clint and the good news is is
that we offer customization of our application to
each tribe, each customer, that buys our application, we
will customize it for them. Now, not all of our
tribes have customization but if they want it, we’ll do it for them. The reason we customize
is that some of our tribes they’ve got additional
functionality that they want and we kind of take the Starbucks approach when we sell our software. You go into Starbucks and
the first thing they say is what can we get started for you today? And the point is is that
you’re getting something that was built just for
you and you’re gonna get it just the way you want it and
that’s the Eaglesun approach. Plex accommodates for
this ability to customize your software for each
release of your software because of the fact that it’s got versions and levels built into the tool. Without a tool like Plex you would never be able to offer this to your customers. But with Plex it allows you to do it and it actually works very well. The other thing is is because
Plex is based on patterns it allows us to build
abstract objects once and then specialize them for each tribe, based on their needs. I say without a powerful
ARAD tool like Plex, we simply couldn’t offer this. This is our competitive
advantage in the space. Now we’re going to talk about the bad. The fact that we can and
do offer multiple versions of our application, it
prevents us from doing a single build of the
application and then deploying that build to all of our tribes. Every time we have a major
release of our software, or a major release of
Plex, it requires that we do a complete gen and build of
each version for each tribe. We’ve got 65 tribes out
there, every one of them we do a complete gen
build of every function. Not only do we have to gen and build the entire application, we have to test the entire application for each tribe because it’s been customized it’s not just a one version of your software, build it and install it. After we gen and build it, we test it, and then our trainers and
installers they go on-site to the tribes, they install the software and they train the users
on the new features of the software. And there’s always a significant
volume of new features. Now let’s talk about the ugly. Within our application a typical tribe will have well over 20,000 functions. As you will know using
Plex, you cannot do a gen and build of your entire
application of 20,000 functions with a single click of the mouse. What will happen is,
Plex has a memory leak during the generation
process, so Plex will crash if you generate too many
objects in one effort. And Visual Studio will start
causing each build to fail after about 390 we’ve
found that 390 is kind of a breaking point of anything after that, what happens is, is that let’s say you do a thousand objects, the
first 390 are successful and then after that they
they’re unsuccessful, they failed and you can’t stop the build. It just goes, and goes, and goes again, you’ve got to kind of start over. It’s very frustrating so what we found is that we always have to break up our builds into units of about 390. If you just do the math you
got 20 thousand functions you’ll do 390 of time you can see that’s a significant effort of having to do this. What, for us, what it
means is that it typically takes several days to do
a complete gen and build of a single tribe and
it’s very labor intensive. Someone sitting there,
pushing the buttons, monitoring it and it’s
prone to human error because if you miss
something, and you wind up with an incomplete
release of your software surfaces during the testing. Okay, we went to the conference in Miami this last October, which
was an amazing conference by the way for anyone who didn’t attend. While we were at that conference we spoke to John Rhodes from CM First
and we had a discussion with him about what our
challenges are at Eagleton. He mentioned that they
have this amazing tool that they have built called
the Plex Auto Gen Tool and it automates everything that we have to do during the entire
gen and build process. We downloaded, installed a
trial version of the tool and I work directly with Kyoshi
during a proof-of-concept project to make sure that the tool works as advertised and it would
meet our needs, and it did. We worked out a couple of
minor issues with the tool and we bought it, and we are
currently using that tool to build our releases of our
application and we love it. What is the Plex Auto Gen Tool? As I mentioned, it was
developed by CM First and it uses the Plex model API. What it does is it automates
unlimited iterations of the entire process of generating and building your application. What it does is you start this tool, it opens your local model, it
generates either a package, a subject area or list depending
on what you choose to use. After the generation does the build, saves your local model,
closes Plex and restarts. Then it goes to the next list. You’re in control of at what point does a save of the local model and closes Plex, restarts Plex, that takes
care of the memory leak and then you’re in control of the size of your subject areas or lists. Like I say, we do
approximately 390 in a group. This thing, you kick it
off and it just runs. On huge builds like we have, this thing is a real game changer. The way the tool works it’s based on two configuration files. They’re a JSON file and
you’ve got one JSON file which contains the list
or the subject areas that you want to build
and this is going to be kind of dynamic, so based on each tribe they’re going to have
different list of subject areas that we’re going to build from. Then you have one which is
kind of a configuration file that just says where’s
your Plex local model live, where does the GenReq.JSON file live and then whether or not you want to save at the end of the build. You can do the gen and build and tell it you don’t want to save, just close Plex, restart Plex and move on. You break it up into units
and you’re in control of exactly how this thing works. Basically once your JSON
files are configured you simply call the CA AutoGen.exe tool and it does all the heavy lifting. Here’s an example of the two JSON files. The one on the top basically is a pointer to where my local model
exists, second line in the top one there it just
says where’s the JSON file for gen request, that’s the
one that contains your list. Whether or not you want
to generate everything or you can just do gen only
or build only whatever. Then where is a where does the Plex exist on your local machine. The second JSON file there
is going to be customized based on your application in your model and that basically contains pointers to the various subject areas
or lists or packages that you’re going to gen and build. That’s basically it. It’s those two configuration files and then you just run the thing. I talked about, it will
either work with packages, lists or subject areas. We use subject areas in
lieu of lists or packages. The reason we use subject
areas, they’re very reusable. During the gen and
build of a subject area, Plex isn’t updating anything. That works great because for us we’ll have multiple developers that are kind of reusing this thing at the same time so we’re not tripping over each other in terms of it trying to update the status of an object and this type of thing. There is a tool out there
called the Plex Upgrade Wizard on the Plex wiki there and it’s free and it can be used if
you choose to use list, you can use that tool
too your list for you of what needs to be gen built basically on your application. We have a custom version of that that we use internally and what it does is it allows us to create
subject areas or lists and within those it allows us to specify how many functions we want in each list. If you got 20,000
functions you run the tool it will build you a list of let’s say, you want 300 functions it will just build you multiple subject
areas, each subject area contains 300 functions. For an entire application it
might build 30 subject areas. Plex Auto Gen Tool, like
I said, you configure your JSON files you run the exe. What it does is it brings
up a command window it’s a black box kind of looks
like a DOS session there. Basically it starts
displaying diagnostic messages as it’s running to kind
of show you where it’s at. When it’s all done you get a message that says is completed
press enter to finish The way it works is is
we’ll start this thing like at 5:00 before we
leave and let the thing run all night. We come in the next
morning, the build is done. On a huge build, we’ll
start the thing on a weekend at 5:00, we come back in
Monday and it has gen and built 20 thousand-plus functions. Who should be using this amazing tool? My recommendation is
anyone out there who has, either a very large application that needs to be done efficiently or
if you have a situation where your application is
gen and build frequently and you’re building large
portions of the application. This tool doesn’t help you if
you’re just doing small builds this is really built for
for very large builds and you need efficiency in that build. The other situation is if
you have many applications that you need to build
and you need to be able to get it done quickly,
this is the tool for you. Links, you’re probably wondering, where can I get this tool
and the first link there is to see CM First and
the second one there is to Mark O’Brien and
he can get you fixed up with this tool, they can
set you up with a demo of the tool, give you some pricing. The tool is very affordable
and for us this tool is worth its weight in
gold because of the fact that based on our business environment we’re going to get a
tremendous value of this tool over the years. I also mentioned the Plex Upgrade Wizard that kind of plays into
this, you might want to use it to build lists
and that’s the link to get that free tool. I says test drive if time permitting and time is not permitting. I’ve used up all of my time
probably and plus some. I would recommend to you that if you have an interest in this tool go to CM First, give Mark a call and he can
give you all of the details and that is the end of my Lightning Talk. I’m going to hand it over to you guys to do Lightning Talk number two. – [Steve] OK, it’s all you Pradeep. – [Pradeep] Good morning all. Today we’ll discuss about Plex Java Build and Debug with ECLIPSE integration. I’ve divided this topic into five. Introduction, installation,
Plex build setup, post setup and debug. First we’ll go through the introduction. Why we need Plex Build and
Java integration with ECLIPSE. We have migrated 2E applications
to web applications. It was necessary first to build
and debug Java source code. We have implemented one step build process which is really easy it just
need to install a plug-in. We have applied standard debug
practices for entire team. I’ll show this through a video. We need this plug-in to
be installed in ECLIPSE. Drop this plug-in in their dropins folder of your ECLIPSE installation. Then launch your ECLIPSE. Go to help, we have option about ECLIPSE. In there, take installation
details and go to plugins tab. You will find the plug-in in there. Then you’ll have the
Plex option in your menu and that will have two
options, Start Plex Service and Stop Plex Service, you
need to start the Plex service. After this, go to your Java project, right click and you will have the option, Add/Remove Plex Nature. Choose the option Add/Remove Plex Nature. And you’re all done here. Go to your local model. Go to Gen and Build options go to Name and Location Parameters and we’ll return a couple of entries here. One, move source and you need
to give a value as false. And another one target
build project and evaluate should be the same name of
your Java project in ECLIPSE. In my case it’s Neptune_Java. Click OK. With this we are done with the setup and we are ready to build
any function we require. We can do it in just one step
and the function gets built. One step build process. Now we’ll go for ECLIPSE,
debugging in ECLIPSE. I will take you through
that with another video. We need to know a few steps like how to install breakpoints,
how to remove breakpoints and we also need to
know step in, step over, and I’ll explain them in this video. Go to the program where you want to which function you on a debug. Highlight the line. Bring the cursor to the line where you want to insert a breakpoint. You can do that by highlighting the line and double clicking on
the blue bar at the left. And if you double click
once again the breakpoint will be removed, if not you can go to Run and you’ll have toggle
breakpoint option at the same. You can insert a breakpoint
with this option. If you want to remove that breakpoint you can do that with
the same option again. I have already inserted
a couple of breakpoints in the code I will show the
debugging process with this. To go ahead with the
debug you need to start the server in debug mode. Launch your application
and choose the menu option which will call your function. The function will automatically start at the first break point in the code. I’ll do F6 which is step out, F6, F6. We’ll go we’ll step over
each each line of code. At any point of time if you
want to go into a subroutine you can do an F5 and I will
show in the coming part. I’m doing F6, F6. At any point of time if you want to skip and go to the next breakpoint instead of doing it line by line, you can do F8. Here we have a subroutine and I will not, I’ll be stepping over this
instead of stepping into it. And I will show step into after this. And also, at any point of
time if you wanna inspect a field as you can do that by going to highlighting the field
and going to Run and Inspect or you can use Ctrl + Shift
+ I to inspect the field. I highlight the field
and do Ctrl + Shift + I or run Inspect so that will
get the value of that field. Next, I am going into the
subroutine by using F5. It brings the control
this subroutine and we can go F6, F6 to step over each line of code. At any point of time if
you want to just come out of the code, you need to
use F7 and it will bring the control back out from the subroutine and you can debug from that point of time. At any point of time
if you wanna terminate the debugging you can go to run and we’ll have option terminate. These are few steps that
we used while debugging. I’ll also tell you the advantages
of using ECLIPSE debugger. It provides break points, watch points and at runtime you can
inspect field values. It also provides various
views for debug perspectives. We’ll have wide range of varieties, wide range of advantages
using ECLIPSE debug using ECLIPSE debugger,
that’s it, thank you. – [Steve] All right, thanks Pradeep. Who’s going to be presenting next? – [Mark] I think we’re into
the wrap up and the Q&A. I did have a question I
don’t know if it’s going to be for Roger or CM First. But on the conversion
utility what versions of Plex are supported by that utility? – [Roger] I would say
probably, certainly 7.1, which is the release
that were currently on and I believe that it
also works with 7.2.1. CM First is probably
going to be the only ones that can answer that for sure. – [Mark] George did post
a question in the Q&A to give a shout out to the
author of that utility. Says she worked with Kyochi
can we give him the credit? – [Roger] Absolutely, absolutely,
Kyochi, he was fantastic. He spent a lot of time
with me talking about it, we kind of worked out a
few of minor little issues that were like configuration type stuff but he really put a lot of
time into it to make sure that we had a successful endeavor as we went through that proof of concept. It is a fantastic tool, we love it, we haven’t had it that long,
but we already love it. I think if you were to
talk to me a year from now I think that we’re gonna
have nothing but success and I would be even more
impressed with the tool the more we use it. – Wonderful.
– I was gonna say, I see another question out there that says in percent, how many
applications will upgrade without human works? I’m going to say probably right now 0% without any human works and
it’s not because of the tool it’s just because the fact
that with our application it’s large and changes have been made over in the model since the last tool. What happens is is that you take something that was gen and built three years ago and then you make changes in your model and then you try and gen and
build it three years later and you always run into
little issues here and there where there’s like
something that got changed but it never did get generated
and so you always find. You know, you got a
little, some cleanup stuff here and there. But this tool does all the heavy lifting. When we say how many
applications will gen and build and upgrade with no human
it’s like, right now, I’m going to say none of them will, but the tool is probably doing 98% of all the heavy lifting. Then we’re able to focus on the 2%. Something that didn’t
generate or didn’t build, why didn’t it build, there’s
always those functions that you’ve got to get in
and research and figure out. But if I think about the the
entire scope of a project, this tool is going to do the vast majority of all that heavy
lifting, it is fantastic. – [Mark] George has a
follow-up question for you. Are you doing nightly builds then? When you have such a large application, you mentioned about running it at night, are you doing those nightly? – Absolutely, well, not every night. But when we run it, we would normally have to do it during the day because you’ve got to sit there and a human
being has got to go through all the process of
batching them up and doing them one at a time, push
a button, drag-and-drop, push a button, whatever. It used to be a very manual effort and now with this tool it basically allows you to put it into kind of a batch environment and then you just start it
and you just let it run. I’m gonna say yes definitely
run it at night unattended and on huge ones we’re
gonna start it on a weekend at 5:00 in the evening and
let it run all weekend. – [Mark] And then Roger,
George posted a follow up. I think, he’s making a
point, that your model is current and it’s up
to date you always know if you’re doing that. And I have a question for you then, are you running like a
regression suite against your applications, as
you’re doing the build? Or you do it like a full CICD process where you have a whole set of regression tests running against it? – [Roger] I’ll be honest
with you, because of the fact that we’ve got basically 65
potential different flavors of our application, it
really doesn’t allow us to use like automated
testing software to do it. We’re trying to move
towards a configuration where we have less
versions of our software. Ultimately, yes, we would love to use regression testing automation and all that type of thing and ultimately to have fewer builds than 65. We would love it if we
could have one build and that build included all
the flavors of our software and then as installed the software based on configuration and that type of thing will run the appropriate
version of the software. Ultimately, yes, we would
like to get to a point where our entire application is one build but we’re a long ways from getting there. For us, the fact that
we’ve got multiple builds of our software and they’re all very large means that without a tool
like this it’s just very, it’s an intensive effort. But this tool really helps
us to be more efficient in how it’s done and to
be faster, and the faster is because the fact that
letting the thing run at night when no one’s sitting there
babysitting the thing, that there’s tremendous value there. – [Mark] We have another
question from the Q&A. This one’s for Jorge, hello Jorge, the question he posed and
I answered within the chat if you guys will follow along
is about a Plex roadmap. We are working on that. Arun and Vijay a which
is your project architect and product owner and myself have come up with a list of the things we’d like to do. We’ve been sorting it down
to the highest priorities. We’re not quite ready to share that in the next community update I’m hoping that we’re going to do
these every other month and it depends on if you guys volunteered to do a Lightning Talk
like Pradeep and Roger. The more that we get volunteers, the sooner we’ll turn these around and the more we’ll do it. But if not, the next time
we do these we are tending to do the Plex roadmap and as soon as we do some more analysis on the features and the size and scoping and feasibility, there are some great things on Jorge’s. I think he’s pitching for two of them. A DotNet generator for
Less, that sounds bigger than what Arun has told me about, but RESTful web services
I’m sure everybody is most interested in
REST and JSON support. We’ll communicate that
and what we’re planning at the next community meeting. Any other questions,
then I have another one if you’re following
along I had answered Lou about technical documentation,
I want to be very clear and I don’t want to seen as avoiding answers. Our documentation, the
way we moved in DocOps to have it online you guys
get to participate without it. There’s something that
is missing something, something is not documented
there’s no intention to have non-documented fixes out there. The DocOps documentation
should be being updated on a regular cadence. It’s one of the reasons
that we asked you guys not to download PDFs. And if you have a CA support ID you can go put comments directly
into the DocOps system and those comments get collected by our technical writer
engineers and then they get graded on them and updated them, just like any other case. If you have the ability
to create a case with CA, you have the ability to post comments into the documentation. I’d say this isn’t clear,
this needs to be updated, this is missing and/or create a case with our support organization
if there’s something that’s either not clear or missing. It is part of our goals not only give you quality software but
quality documentation as part of that. We have a fairly large tech
writing organization in CA, we call DocOps for short
and they have goals to make sure that when you
do any kind of feedback on our products that
documentation is rated very high. If we’ve got a gap in
there, if you see something that’s not correct, bring it up. You’re always welcome
to send it to me also as the product manager,
I’ll be happy to address it with our our scrum team and
our and our DocOps team. Any other questions? I have to say that if you use Obsidian and you may not have
the big problem with 390 wouldn’t see functions at a time. if you guys are using an Obsidian utility you may also have a solution already. Andreas, I think you can
you volunteer to do a demo the next time? Drop us a note if you
want to show what you guys are doing with 10,000
functions using Obsidian. This call is a community call. I know we’ve got a lot of CM First, but all of the partners
anybody you guys want to see is tips and tricks across the board. All right, I don’t see
any other questions. Mark, Roger, Pradeep
are we good to wrap up? – [Mark] I believe so. – [Steve] All right, thank
you everybody for attending. If you’d like to volunteer
you get a nice little thank you and and you can
be known from your peers. Also you’ve heard Roger
pitch the conference, it was phenomenal, I think
if you would have come and you would got some of those tips you would have paid for your travel just in a couple hour conversation. Hopefully we can get together next time. We’ll have even more to talk about. Thank you for attending
and please look forward to the next one. Stay tuned to the community for the next community meeting announcement. Cheers, bye.

Robin Kshlerin