From ea871f751cad553dd4bff973d24ef10dd13603ac Mon Sep 17 00:00:00 2001 From: Zach Lasiuk <18421034+zachlasiuk@users.noreply.github.com> Date: Wed, 17 Jul 2024 07:15:08 -0500 Subject: [PATCH] Update datapoint-boundary-conditions-commercial.md --- datapoint-boundary-conditions-commercial.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/datapoint-boundary-conditions-commercial.md b/datapoint-boundary-conditions-commercial.md index 0015bd95..d6f70d50 100644 --- a/datapoint-boundary-conditions-commercial.md +++ b/datapoint-boundary-conditions-commercial.md @@ -53,13 +53,10 @@ A unique software package from an ISV meets these criteria: - It can be purchased from the ISV - It can be singularly purchased - It can be downloaded / installed by developers -- (when confusing) It is not a subcomponent of a broader, already identified software package suite - unless it is independently downloadable. Examples in SAS and Liferay below. - -If undetermined Arm support => ??????? Infra guidance on what to do. Ignore, say True, ask ISV, etc.???????? ## Examples -| ISV | Products | Rational | +| ISV | Products into Dashboard | Rational | | ----------------------------------------------- | ----------- | -------- | | [SAS](https://www.sas.com/en_us/home.html) | SAS Viya | All SAS products are built from the SAS Viya software platform; this is the core package offering, which includes services built on top of SAS Viya (like SAS Data Engineering) | | [Liferay](https://www.liferay.com/offerings) | Liferay DXP, Liferay Commerce | Liferay Commerce is built on Liferay DXP, but is a uniquely obtainable package from Liferay DXP and should be distinct. In addition|